Get customer

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful context that the response includes loyalty points and visit history totals, but it does not disclose error behavior, idempotency oddity, or any rate/authentication considerations.

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?

One clean, front-loaded sentence contains the operation, scope, and key return fields with no filler.

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 single-parameter read operation with readOnly annotations, the description covers the essential operation and the notable return fields. It omits what happens on a missing customer or how to obtain the customer_id, but those gaps are minor for this simple 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?

With 0% schema description coverage, the description must compensate, but 'by id' only restates what the parameter name customer_id already communicates. It provides no format, source, or uniqueness information for the id, adding minimal meaning beyond the schema.

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 uses the specific verb 'fetch' with the resource 'one customer by id', clearly distinguishing it from list/upsert siblings. The added detail on loyalty points and visit history totals further specifies this tool's unique return content among the sibling get 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?

The phrase 'one customer by id' implies this is for a single known customer, while list_customers would be for multiple, and upsert_customer for creation/update. However, no explicit when-to-use or when-not-to-use guidance naming alternatives is provided.

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