get_top_customers

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

The description states 'Lists top N customers' which implies a read-only, non-destructive operation. However, the annotation destructiveHint is true, directly contradicting the description. No additional behavioral traits are disclosed beyond the contradictory annotation.

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 concise with a single sentence that contains no superfluous words. It front-loads the core action 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?

The description lacks critical context: no details on the return format, whether results are sorted, pagination behavior, or what fields are included. Given the tool's simplicity (one parameter, no output schema), it is incomplete for an agent to use reliably.

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% for the single parameter 'limit'. The description adds marginal value by implying that 'N' in 'top N customers' comes from the limit parameter, but does not specify bounds, format, or semantics beyond what the schema provides.

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 the verb 'Lists', the resource 'top customers', and the criterion 'by order count'. This uniquely identifies the tool's function and distinguishes it from sibling tools like 'get_daily_sales' or 'get_pending_orders'.

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 description provides no guidance on when to use this tool versus alternatives. No when-to-use, when-not-to-use, or contextual cues are given. For example, it does not mention that this tool is for customer ranking specifically, as opposed to sales summaries.

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