xero_contacts_get

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

The description implies a read operation and lists return fields, but with no annotations, it misses opportunities to disclose behavioral traits like authentication requirements, idempotency, or potential errors. It is adequate but not thorough.

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?

Two sentences with no extraneous information. Every word serves a purpose: states action, method (by ID), and return content. Highly efficient.

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?

For a simple one-parameter get tool without an output schema, the description is nearly complete. It explains what the tool does and what it returns. Missing minor details like error handling or response structure, but those are not critical given the tool's simplicity.

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 100% and the description of contactId in the schema is clear. The tool description adds that it returns 'addresses, phone numbers, and email,' but parameter semantics are already well-covered by the schema. Baseline 3 is appropriate.

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 action ('Get detailed information') and the resource ('a specific contact by its ID'). It distinguishes from siblings like xero_contacts_list and xero_contacts_search by specifying 'a specific contact' and mentioning the return of detailed profile fields.

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 does not provide explicit guidance on when to use this tool versus alternatives (e.g., xero_contacts_search). It does not mention prerequisites or conditions, leaving the agent to infer usage from the tool name and context.

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