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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral context by disclosing the ranking order (by filing volume) and that prosecution and TTAB activity counts are included, which goes beyond the structured annotation fields. It does not overstate or contradict 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?

Two sentences with no filler: the core behavior is front-loaded in the first clause, and the example question reinforces the intended query pattern. Every sentence earns its place.

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 ranked-list tool with a fully covered input schema, rich annotations, and an output schema, the description is nearly complete. It lacks only an explicit pointer to alternative tools for related but different questions, such as a single correspondent's marks or specialization.

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 100%, so the baseline is 3. The description confirms firm_name refers to a named law firm but does not add anything about limit or accepted key formats beyond the schema, so it neither improves nor worsens parameter clarity.

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?

Description uses a specific verb ('Ranks') and clearly identifies the resource ('correspondents or attorneys within one named law firm') and the ranking criterion ('by filing volume'). The mention of prosecution and TTAB activity counts further distinguishes it from sibling tools like get_firm_correspondent_tasks or get_top_filers.

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 the use case with an example question ('who the top correspondents at Fross Zelnick...'), so an agent can infer when to call it. However, it gives no explicit when-to-use guidance, no exclusions, and does not compare against alternative tools such as search_attorneys or get_firm_correspondent_tasks.

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