Get customer

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

With readOnlyHint/idempotentHint/openWorldHint already declared, the bar is lower, yet the description still adds real context: it reveals the tool fans out to two endpoints (GET /customers-suppliers/{id}/ and GET /orders/?customer={id}&ordering=-issue_date) and that sensitive fields are gated behind include_contact_details by default.

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?

Front-loaded with the high-value payload description, then conditional caveats, then endpoint detail. Dense but no filler; the endpoint citation is the only slightly marginal element.

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?

No output schema exists, so the description carries the return-value burden and does it well by enumerating returned fields and conditional inclusions. Combined with full schema coverage, an agent has everything needed to call it correctly.

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%, so baseline is 3, but the description adds value beyond the schema by spelling out the field groups that appear only when include_contact_details is set (contacts, addresses, tax number, custom fields) and by framing recent_orders as the newest-first ordering implied by ordering=-issue_date.

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?

States a specific verb and resource ('One customer in full') and immediately enumerates the exact fields returned, which lets an agent distinguish it from list_customers without opening anything. The scope is unambiguous.

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?

Usage is implied by the singular 'one customer' plus a required customer_id, and the description notes that contact/address data only arrives with include_contact_details. However it never explicitly states when to pick this over list_customers or that it is a read-only single-record fetch.

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