xero_upload_file

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

With no annotations, the description should disclose behavioral traits. It only mentions routing through an API endpoint and scope, but does not clarify whether the operation is destructive, its side effects, or any prerequisites. Transparency is minimal.

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 not efficiently structured. It includes irrelevant routing details and redundant naming ('Xero connector operation upload_file'), while omitting essential information. It wastes space without delivering value.

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 file upload operation, the description is critically incomplete. It fails to specify how to provide the file, what file types are supported, or any expected response. The presence of an output schema is irrelevant if the agent cannot understand how to invoke the tool correctly.

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 defines the single parameter 'arguments' as a 'JSON string of arguments for the connector operation.' This adds no meaningful detail about expected keys, file content, or format. The agent cannot infer how to construct valid input.

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 states 'upload_file' but does not specify what kind of file is being uploaded or to where within Xero. It does not differentiate from sibling tool 'xero_upload_attachment', which likely serves a similar purpose. The purpose is vague and lacks specificity.

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 provides no guidance on when to use this tool versus alternatives. No when-to-use or when-not-to-use conditions are mentioned, leaving the agent without decision criteria.

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