aruba_parse_notification_xml

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, indicating safe read operation. Description adds no extra behavioral context (e.g., error behavior, validation, or data format specifics).

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?

Description is a single concise sentence but lacks critical detail. It is front-loaded but too minimal to serve an effective purpose.

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?

Even though output schema exists, the description fails to explain return structure, possible errors, or input validation. For a parsing tool, such context is essential but missing.

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 0%, meaning parameters are undocumented in schema. Description does not elaborate on the single parameter 'xml_base64' – no format, encoding, or usage details beyond its name. This is insufficient for correct usage.

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 action ('Parse'), the input ('Base64 SDI notification XML'), and the output ('structured fields'). It distinguishes from sibling tool 'aruba_parse_invoice_xml' by specifying notification XML.

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 on when to use this tool vs alternatives like aruba_parse_invoice_xml. No prerequisites or when-not-to-use instructions provided, leaving the agent uncertain about appropriate usage.

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