xero_create_quote

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

No annotations are provided. The description only mentions routing through an endpoint with JWT/tenant/company scope. It does not disclose that this is a write operation or any side effects, rate limits, or required permissions beyond authentication.

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 very short (3 lines) but lacks substance. It front-loads the tool name redundantly but fails to provide essential information, making it under-specified rather than concise.

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 the low schema coverage (0%), the description should compensate with detailed parameter guidance. It fails to do so, leaving the agent completely in the dark about how to construct the arguments JSON. Although an output schema exists, the description does not help with invocation.

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 a single 'arguments' string parameter with 0% description coverage. The description only says 'JSON string of arguments for the connector operation,' which adds no meaning beyond the schema. The agent has no idea what fields to include in the JSON string.

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 creates a quote, but lacks elaboration on what a quote is in Xero context. The name and verb are clear, but no additional clarification beyond restating the tool name.

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 like xero_list_quotes or xero_update_quote. No explicit use-case or exclusions provided.

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