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

Annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower. The description adds genuinely useful behavioral detail beyond them: the computation performed (revenue per hour with total/average and a below-average flag) and the concrete output artifact (a link to an external calculator). It omits limits such as the 30-client maximum, but the external-link behavior is 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?

Three sentences, front-loaded with the core action, then usage intents, then the return artifact. Each sentence earns its place, though the usage sentence is slightly long relative to the rest.

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?

There is no output schema, so the description's explanation that it returns a link to an external calculator is important and present. It does not mention the 30-item input cap, a minor omission given how thoroughly the computation and return value are described.

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 description coverage is reported as 0% at the top level, and the description supplies no information about the clients payload. However, the nested schema does describe client, monthly_fee, and hours_per_month individually, so the schema itself carries most of the semantic load and a baseline 3 is appropriate.

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 states a specific verb and resource ('Rank a consultant's clients by revenue per hour') and enumerates exactly what the output contains: totals, average, and a below-average flag. This is clearly distinguishable from sibling tools like calculate_consulting_rate or check_capacity.

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?

It gives concrete triggering intents ('which clients are worth keeping, which to raise prices on, or why they're busy but not earning more'), which is strong context. It does not, however, name or exclude any sibling tool (e.g. calculate_consulting_rate) even though their subject matter overlaps.

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