get_top_customers

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

The description claims a read-like operation ('Lists'), but annotations set destructiveHint=true, indicating potential mutability. This contradiction undermines transparency. No additional behavioral traits (side effects, permissions) are disclosed beyond the annotations.

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 that immediately communicates the tool's purpose without unnecessary words, achieving high readability and front-loading.

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?

For a simple tool with one parameter and no output schema, the description covers the essential functionality. However, the contradiction with annotations and lack of output details slightly reduce 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?

The description adds meaning beyond the schema by specifying that the 'limit' parameter controls the top N customers and that ordering is by order count. The schema only describes the parameter as 'limit (integer)' with string type, so the description provides useful context.

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 'Lists top N customers by order count' uses a specific verb ('Lists') and resource ('customers') with a clear criterion ('by order count'), distinguishing it from sibling tools that deal with tables, procedures, or database queries.

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 implies usage for retrieving top customers, but it does not explicitly state when to use this tool versus alternatives like get_daily_sales or get_pending_orders, nor does it provide any exclusions or prerequisites.

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