get_customer

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

With no annotations provided, 'Get' implies a safe read-only operation, but the description omits error handling, authorization requirements, and what constitutes 'detailed' information.

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?

Single sentence, front-loaded with action verb, no redundancy. Every word earns its place in defining scope and resource.

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?

Adequate for a simple single-parameter getter, but given the lack of output schema and annotations, the description should ideally specify error behavior or the structure of the 'detailed information' returned.

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% and the parameter is already well-described. The description mentions 'by their ID' which aligns with the schema but adds no additional semantic clarity beyond the schema definition.

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 specific action (Get), resource (customer), and scope (single by ID). The 'single' qualifier distinguishes it from the sibling list_customers tool, though it doesn't explicitly name the alternative.

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?

Implies usage context (when you have a specific ID) through 'by their ID', but lacks explicit guidance on when to prefer list_customers or error scenarios like 'customer not found'.

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