xero_create_receipt

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

No annotations are provided, so the description carries the full burden. It only mentions routing and scope, but fails to disclose that this is a write operation, whether it is idempotent, or any side effects. The behavioral impact is unclear.

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 contains redundancy (e.g., repeating the tool name) and includes low-value routing details. It could be more concise and focused on the tool's purpose.

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?

The description lacks essential context such as what a receipt represents in Xero, required permissions, typical usage scenarios, and error handling. While an output schema exists, it is not explained.

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 'arguments' is described as a JSON string, but this adds little beyond the schema which already specifies it as a string. No details on required keys or structure are given.

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 indicates it's a Xero connector operation for creating a receipt, but it doesn't specify what type of receipt (e.g., expense or sales) or differentiate it from similar create tools like xero_create_invoice or xero_create_bill. The name 'create_receipt' is clear, but the description 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?

No guidance on when to use this tool versus alternatives such as xero_create_invoice or xero_create_bill. The description only explains the routing and arguments, not usage context.

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