xero_create_statement

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, required permissions, idempotency, or rate limits. The only extra information is about routing and JWT, which does not inform the agent about the tool's behavior.

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 includes unnecessary routing details (e.g., '/api/tools/invoke' and scope info) that are not helpful for an agent selecting the tool. It could be more concise by focusing on the operation'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?

Despite having an output schema (not shown), the description does not explain what the tool returns or what a statement creation entails. There is no guidance on how the single argument should be structured. The description is insufficient for an agent to use 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?

The input schema has 0% description coverage, meaning the single parameter 'arguments' has no documentation. The description adds no meaning beyond the schema, leaving the agent with a JSON string whose structure and required fields are unknown.

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 it is a Xero connector operation to create a statement, but it does not explain what a statement represents in Xero (e.g., bank statement, reconciliation statement). It adds no context beyond the tool name, making it barely distinguishable from other 'create' tools. The description is more about routing than purpose.

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 is provided on when to use this tool versus alternatives. There are many Xero tools (e.g., xero_create_invoice, xero_create_bank_transaction) and no differentiation or prerequisite conditions are mentioned.

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