get_customer

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

Annotations indicate readOnlyHint and idempotentHint are true, so the description does not need to restate these. The description adds no further behavioral context (e.g., no mention of side effects, auth, or rate limits), but it doesn't contradict annotations. A score of 3 is appropriate as the description is neutral and adequate.

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, concise sentence. It is front-loaded and directly states the tool's purpose. However, given the lack of parameter guidance, it could be slightly more structured, but overall it is appropriately brief for a simple tool.

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?

With a simple tool (one parameter, output schema present), the description is minimally complete. It states the purpose but does not explain that it retrieves a single customer by ID or describe the output. The presence of an output schema partially compensates, but the description could be more helpful.

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 has one required parameter (customer_id) with no description. The tool description does not mention or explain this parameter, leaving the AI agent without semantic meaning. With schema coverage at 0%, the description provides no value beyond the schema itself.

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 'Detalle de un cliente' clearly indicates the tool retrieves details of a customer. The verb 'get' in the name aligns with the purpose. While it doesn't explicitly differentiate from sibling tools like list_customers, the singular nature and the specific noun 'customer' make the purpose evident.

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 is provided on when to use this tool versus alternatives. For example, there is no mention of when to use 'get_customer' over 'list_customers' based on needing a single record versus multiple. The description lacks context for appropriate usage.

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