xero_get_attachment

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

No annotations are provided, and the description does not disclose whether the tool performs a read, download, or destruction. The routing note is generic and does not reveal side effects or required permissions.

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 short but wastes space on redundant boilerplate (e.g., connector operation name) and lacks operational specifics. It is concise but not informative.

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?

Despite an output schema existing, the description does not explain the tool's purpose, input structure, or effects. An agent cannot determine when to call this tool or how to structure the arguments, making it incomplete.

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 schema has a single 'arguments' parameter with no description (0% coverage). The description adds that it is a 'JSON string of arguments for the connector operation,' but this is generic and does not specify valid keys or formats, adding minimal value.

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 name suggests retrieving an attachment, but the description only states it's a connector operation without specifying what 'get_attachment' does (e.g., retrieve a file by ID, metadata, etc.). It lacks a clear verb-resource pairing and does not distinguish from sibling tools like xero_list_attachments or xero_upload_attachment.

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, required identifiers, or context for invocation.

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