xero_quotes

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

With no annotations, the description carries full burden. It only states a read operation ('Get quotes'), but fails to disclose any behavioral traits such as pagination, filtering behavior, rate limits, or whether it retrieves all quotes or only recent ones.

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 a single sentence, which is concise but overly sparse given the complexity of the tool (4 parameters, no schema descriptions). It is not structured with any additional information that could aid the agent.

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?

The description is severely incomplete. It lacks context on authentication (access_token, tenant_id), filtering options (status, contact_id), output expectations (no output schema), and any behavioral notes. With 4 parameters and no annotations, much more detail is required.

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 description adds no meaning to the 4 parameters (status, contact_id, access_token, tenant_id). With 0% schema description coverage, the agent has no insight into how to use these parameters effectively.

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 'Get quotes from Xero' clearly states the action (get) and resource (quotes), distinguishing it from sibling Xero tools like xero_accounts, xero_invoices, etc. However, it lacks any additional detail about the scope or nature of the quotes.

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 (e.g., xero_invoices for invoices, xero_reports for reports). There is no mention of prerequisites, authentication context, or scenarios where this tool is appropriate.

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