GET /customer/:id (Customer)

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

Annotations already indicate read-only safe operation. The description adds that returned data depends on software version (via a referenced table), which provides some context beyond annotations, but fails to disclose other behavioral traits like authentication requirements or rate limits.

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 short and front-loaded with the purpose, but the vague reference to a table that is not included makes it incomplete. Every sentence should earn its place; the second sentence is unhelpful without the table.

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?

Given one parameter, no output schema, and annotations present, the description is partially complete. It mentions a table of return values but does not provide it, leaving the return format ambiguous. For a simple retrieval tool, more explicit output details would improve completeness.

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 100% schema coverage, the description adds no extra meaning beyond the schema's parameter description. Both state the parameter is the ID from the route. No examples or format details are provided.

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 it retrieves customer data, matching the tool name and title. However, it does not explicitly differentiate from sibling tools like list_customers or search, and the mention of an absent table reduces clarity.

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?

No guidance on when to use this tool versus alternatives. It does not specify that it fetches a single customer by ID while list_customers is for list operations.

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