Join our Newsletter — 33% off our NHI Course

Could parsing ambiguity make MCP tool descriptions miss the right tool?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20217
Topic starter  

TL;DR: Weak MCP tool descriptions can keep a sound tool from being selected, according to Archestra, because the model reads the description, schema names and parameter text at selection time. Agent governance has to treat tool copy as part of the access path, not as optional documentation.

Editorial analysis by NHI Mgmt Group, based on content published by Archestra: “MCP Tool Description: Why It Is a Prompt, Not Documentation”.

Key questions

Q: Why do hedged MCP descriptions reduce reliable tool use?

A: Hedged wording lowers the model’s confidence about when a tool is appropriate, especially when another tool has a sharper trigger phrase or a more direct description.

Q: How should teams write MCP descriptions for overlapping tools?

A: Describe the specific job, the user signal that should trigger the call, the cases where the tool should not be used, and the shape of the output.

Q: What breaks when MCP tool descriptions are treated as harmless documentation?

A: Security teams miss a second instruction channel that can steer the model even when the package is clean.

Practitioner guidance

  • Audit every MCP tool description for selection clarity Replace hedged copy with a verb-led statement, a concrete trigger, a clear do-not-use condition and a short return shape.
  • Add negative cases to overlapping tools Where two tools can plausibly satisfy the same request, specify the boundary between them so the model knows which one to choose first.
  • Review schema property descriptions as routing signals Make parameter descriptions explicit enough that the model can infer required inputs without treating the field as a generic hint.

Bottom line: Weak MCP descriptions can suppress correct tool selection even when the schema and backend are sound.

Glossary terms: MCP Tool Description, Tool Selection Manipulation, Parsing Ambiguity, Description-Driven Governance

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20707
 

Tool descriptions are now a governance control, not a documentation convenience. The article shows that the model reads descriptions at the moment of action, so wording quality directly affects whether a tool is selected at all. That makes the description field part of the operational identity of the tool, especially where agents mediate access to data or workflow functions. Practitioners should treat this as a control design problem, not a copy-editing problem.

A few things that frame the scale:

  • 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.

A question worth separating out:

Q: Should identity teams treat MCP tool descriptions as part of access governance?

A: Yes. In agentic environments, the description is part of how access is exercised because it influences whether the model routes to a capability at all. If the text is ambiguous, the governance intent behind the tool can be diluted before any authentication or authorization decision is enforced. Treat the wording as a control surface, not a note field.

👉 Read our full editorial: MCP tool descriptions shape model selection more than schemas do


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.