Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of explaining behavior. It discloses the output ('returns the tag's text value') and conveys a read-only intent, but it does not address missing tags, multiple matches, invalid XML, or namespace handling. Basic behavior is clear, but edge cases are not covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences with the action and inputs front-loaded. It states what the tool does, what to provide, and what will be returned, with no unnecessary detail or repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with five optional string parameters and no annotations or output schema, this description is incomplete. It does not explain the 'path' parameter despite the tool name, does not state behavior for multiple or missing tags, and does not describe error handling, leaving an agent to guess in common scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by naming xml and tag as the relevant inputs, but it does not clarify the purpose of the other optional parameters, especially 'path', which is significant given the tool name 'xml-path'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific operation: extract the text content of a tag from XML and return it. It is distinguishable from sibling XML tools like xml-to-json and xml-validate, though the tool name and 'path' parameter introduce some ambiguity about whether this uses tag names or XPath expressions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear usage context ('Extract text content of a specified tag from XML') and tells the caller what to provide ('xml and tag'). It does not name alternative tools or explicitly say when not to use it, but the usage pattern is directly stated rather than merely implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.