xero_quotes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no pagination behavior, no result ordering, no note about tenant scoping or rate limits. For an open-world API call, the description could have contributed useful behavioral context but doesn't.

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?

One sentence is technically efficient, but here the brevity is under-specification rather than conciseness. The sentence is front-loaded but omits nearly all the information an agent needs.

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?

A four-parameter, open-world, authenticated API tool with no output schema and no parameter documentation cannot be called correctly from this description. Neither the authentication requirement nor the filter semantics nor the response shape is addressed.

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 description coverage is 0% for 4 parameters, so the description carries the full burden and completely fails. It never explains what 'status' values are valid, why 'tenant_id' is needed, how 'contact_id' filters quotes, or that 'access_token' is an auth credential.

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 verb+resource 'Get quotes from Xero' is identifiable, and the resource (quotes) is distinct from sibling resources like xero_invoices or xero_payments. However, it doesn't clarify whether this lists all quotes, retrieves a single quote, or filters them, and it never differentiates itself from the other Xero tools in any concrete way.

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?

There is no guidance on when to use this tool versus xero_invoices or other Xero siblings, no mention of prerequisites (tenant/access token), and no indication of what the optional filters do. An agent has to infer everything from the parameter names alone.

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