xero_upload_attachment

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

No annotations are provided, so the description must disclose behavior. It only mentions routing details (JWT, tenant, company scope) but does not describe the actual operation's effects, required permissions, or whether it is destructive/idempotent.

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 concise at three sentences, but much of the content (routing info) is of low value to an agent. It could be restructured to front-load the purpose and key constraints.

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 having a single parameter and an output schema, the description fails to explain the necessary argument structure or the tool's expected outcome. The routing details are irrelevant to the agent's decision to use the tool.

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%, and the description only states that the single 'arguments' parameter is a JSON string. It does not explain what fields the JSON should contain, leaving the agent without necessary context to invoke the tool correctly.

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 tool name 'upload_attachment' suggests a verb+resource, but the description does not specify what entity the attachment is uploaded to (e.g., invoice, contact). It mentions it is a Xero connector operation, but lacks explicit purpose relative to sibling tools like xero_upload_file.

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 versus alternatives such as xero_upload_file or other attachment-related tools. The description provides no usage context or prerequisites.

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