xero_agent_create_proposal

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

Discloses the non-final nature of the action (queues approval), which is critical. However, with no annotations, the description does not cover other behavioral aspects such as required permissions, side effects, or what happens after approval.

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?

Extremely concise: one sentence of 8 words. Every word adds value, front-loading the action and resource.

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?

For a simple tool with one parameter and output schema existing, the description covers purpose, key behavioral trait, and param format. Could be more complete with JSON schema or example, but is 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?

Schema coverage is 0%, so the description must compensate. The phrase 'Body is JSON' adds format guidance but does not specify the expected JSON structure. Scores a baseline 3 with slight improvement from the hint.

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?

Clearly states the action 'Create a Xero proposal' and includes the key detail that it queues a human-in-the-loop approval. Distinguishes from sibling tools like xero_create_quote or xero_create_invoice.

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?

Implies usage context by stating 'queues an HITL approval', indicating this tool is for creating proposals that require approval. Does not explicitly mention when not to use or alternatives, but the context is clear.

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