xero_invoices_get

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

No annotations are provided; the description covers basic behavior (returns full details including line items, amounts, payment status) but lacks details on error handling, authentication, or rate limits. It is adequate for a read operation but not comprehensive.

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 two sentences, front-loaded with the main action and purpose, with no redundant words. Every sentence adds 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?

With a simple one-parameter tool and no output schema or annotations, the description covers the essential info including what is returned. It could be enhanced by mentioning potential errors or the ID format, but it is largely sufficient.

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 single parameter invoiceId has 100% schema coverage with a clear description. The tool description adds no further meaning beyond 'by its ID', so baseline score applies.

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 clearly states 'Get detailed information about a specific invoice by its ID', specifying the action (get), resource (invoice), and distinguishing it from siblings like list or create by mentioning 'specific' and 'by its ID'.

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 implies using this tool when you have an invoice ID and want full details, but it does not provide explicit guidance on when to use it versus alternatives like xero_invoices_list or xero_invoices_search, nor does it mention when not to use it.

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