xero_get_invoice

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

With no annotations, the description must disclose behavioral traits. It only mentions routing details (JWT, tenant, company scope) but not whether the operation is read-only, what side effects occur, or authentication specifics. The agent cannot infer the tool's safety profile.

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 and front-loaded, but it sacrifices essential information. Every sentence is present but some are unnecessary (routing details) while critical info is missing.

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 an output schema, the description does not reference it or explain the return value. The parameter is underspecified. For a simple get tool, the description should at least clarify what the 'arguments' JSON should contain.

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%, so the description must compensate. It says 'arguments: JSON string of arguments for the connector operation' which is too generic. It fails to specify the expected structure (e.g., invoice ID) or provide examples, leaving the agent guessing.

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 only states 'get_invoice' without explaining what it retrieves or how it differs from other Xero tools like xero_list_invoices. It provides no specific purpose beyond the name, bordering on tautology.

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_list_invoices or other retrieval tools. The description lacks any context about appropriate usage scenarios.

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