getCustomer

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

No annotations are provided, and the description gives no behavioral information such as read-only status, error behaviors, or response format. The word 'Get' implies a read operation, but this is not explicitly stated, and no other behavioral traits are disclosed.

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 extremely short, but this is under-specification rather than conciseness. It lacks essential information needed for correct tool usage, and the brevity does not serve the agent's needs.

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 the generic name and the existence of many sibling tools with overlapping purposes, this description is completely inadequate. It does not clarify what the tool returns, what the customerId refers to, or any operational context, making it impossible for an agent to confidently select and use this 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?

The input schema has one required parameter, customerId, with no description, and the tool description does not explain what this parameter represents or how it is used. Schema coverage is 0%, and the description fails to compensate, offering zero semantic value for the parameter.

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 'Get customer' simply restates the tool name without adding any specificity about what customer data is retrieved or how it differs from sibling tools like getCustomerDetails or getCustomerCoupons. It is essentially a tautology, providing no distinct purpose.

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. There is no mention of use cases, prerequisites, or exclusions, leaving the agent to guess which 'get' tool to invoke.

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