get_customer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It accurately describes the read-only nature (Fetch) and specifies the fields returned. It includes the important behavioral detail that SyncToken is required for edits, adding value beyond a simple 'get' statement.

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 that packs essential information: purpose, return details, and a key usage hint. It is concise and front-loaded with the main action. Minor improvement could be splitting into two sentences for readability, but it is effective.

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 get-by-ID tool with one parameter and no output schema, the description sufficiently covers the return values and hints at the editing workflow. It does not mention error handling or authentication, but given the tool's simplicity, it is adequately complete.

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 input schema covers 100% of parameters with a description for 'id'. The description adds meaning by stating 'Fetch a single customer by ID', reinforcing that the ID identifies a customer, and mentions that the response includes SyncToken, which is relevant to the id's use in subsequent edits.

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 'Fetch a single customer by ID', specifying the verb and resource. It distinguishes from sibling tools like list_accounts or query, and from other get_* tools by mentioning customer-specific details like SyncToken, hierarchy, and balance.

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 explicitly notes that the returned SyncToken is 'needed for edits', which implies that this tool should be called before edit_customer. It provides clear context for when to use the tool, though it does not explicitly mention when not to use it or alternatives.

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