xero_invoices

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

With no annotations, the description should disclose behaviors like return limits, pagination, or authentication needs. It only states the action, missing key traits that agents rely on.

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 single sentence is concise but borderline under-specified. It earns its place but could be more informative without becoming verbose.

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?

Given 6 parameters with 83% undescribed, no output schema, and no required fields, the description is severely incomplete. It does not clarify what is returned or how filters work.

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 only 17% (status described). The description adds no meaning to any parameter, failing to compensate for the incomplete schema. Agents are left guessing the purpose of 5 out of 6 parameters.

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 'Get invoices from Xero' clearly states the verb 'get' and the resource 'invoices from Xero', distinguishing it from sibling tools like xero_accounts and xero_contacts. However, it lacks explicit differentiation or scope mention.

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 compared to other Xero tools or alternatives. Prerequisites like authentication are not mentioned, leaving the agent without context for correct invocation.

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