xero_list_quotes

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. It does not indicate whether the operation is read-only, has rate limits, or what side effects (if any) occur. The technical routing detail ('/api/tools/invoke') does not compensate for missing behavioral context.

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 but lacks substance. It is minimally concise but fails to provide necessary details, making it under-specified rather than efficiently informative.

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, the description is grossly inadequate. With no annotations and only one parameter without schema coverage, the agent cannot determine how to invoke the tool correctly or what to expect from the response.

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 only parameter is a JSON string 'arguments' with schema coverage 0%. The description does not explain how to construct this JSON (e.g., what fields like 'Status', 'DateFrom', 'Page' are available). The agent is left entirely without guidance on valid inputs.

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 merely restates the tool name ('list_quotes') and notes it is a Xero connector operation, but does not explain what listing quotes entails (e.g., whether it returns all quotes, supports filters, or pagination). It fails to distinguish from sibling tools like xero_list_invoices or xero_create_quote.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, filtering capabilities, or scenarios where other Xero tools might be more appropriate.

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