xero_contacts

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

With no annotations provided, the description fails to disclose behavioral traits such as read-only nature, authentication requirements (implied by parameters but not stated), pagination, rate limits, or error handling. The phrase 'Get contacts' implies reading but does not elaborate.

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 extremely concise with a single sentence. While succinct, it may be too terse given the complexity of the tool. The brevity is efficient but at the cost of missing critical details.

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?

Considering the tool has 5 parameters, no output schema, and no annotations, the description is woefully incomplete. It does not cover authentication, filtering behavior, return format, or any other context needed for an AI agent to correctly invoke the tool.

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%, meaning no parameter descriptions exist. The description 'Get contacts from Xero' adds no meaning to the five parameters: search, is_supplier, is_customer, access_token, and tenant_id. It does not explain how these filters work or that authentication parameters are required.

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 contacts from Xero' clearly states the action (get) and resource (contacts). It is not a tautology and gives a basic understanding. However, it does not elaborate on the scope (e.g., all contacts or filtered) to distinguish from potential future sibling tools.

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 other Xero tools like xero_invoices or xero_accounts. No mentions of prerequisites, alternatives, or scenarios where this tool is appropriate. The description offers no context for decision-making.

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