xml_xml_findall

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

The description states the output structure (tag, text, attrs) but does not disclose any behavioral traits such as error handling, performance implications, or side effects. Since no annotations are provided, the description carries the full burden and falls short of being comprehensive.

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 extremely concise with two sentences that front-load the purpose. Every sentence is valuable and there is no wasted text.

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?

Given the simplicity of the tool (two parameters, no annotations), the description provides the core purpose and output structure. However, it lacks examples, error handling, and specific usage context, making it only minimally complete.

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?

The input schema has 0% description coverage, and the description adds no extra meaning beyond the parameter names 'xml_string' and 'xpath'. It does not clarify expected formats, constraints, or examples.

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 the tool returns all elements matching an XPath expression, using a specific verb and resource. However, it does not explicitly differentiate from sibling tools like xml_xml_find, which likely returns the first match.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, limitations, or comparison with other XML tools like xml_xml_find or xml_xml_extract.

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