xero_contacts_get

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a full contact profile including addresses, phones, and email, but does not mention other behavioral traits like read-only nature, authentication requirements, or any side effects. Adequate but not comprehensive.

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 two sentences (20 words) and front-loads the key action and resource. Every word adds value with no fluff.

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 tool is simple (one parameter, no output schema), and the description adequately explains what the tool returns (full profile). It covers the main return fields. Could mention that the output matches list fields for a single contact, but not necessary. Complete enough for a get operation.

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 100% for the single parameter contactId, which is already described as 'The unique contact ID (UUID)'. The description adds only 'by its ID', which is redundant. No additional meaning beyond the schema, so baseline 3 applies.

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 clearly states the verb 'Get' and the resource 'specific contact by its ID', and specifies the return content (addresses, phone numbers, email). It distinguishes from sibling tools like xero_contacts_list and xero_contacts_search by indicating it retrieves a single contact with full details.

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 implies usage when you have a specific contact ID and need full details, but does not explicitly mention when not to use it or provide alternatives like list or search. The context is clear but lacks exclusion or comparison with siblings.

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