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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description goes further by revealing the shape of the result (parentheticals written by judges, verbatim quotes, pin cites, signals) and the important limitation that only top-ranked ~50 citers are included. Pagination/ordering beyond that is not spelled out, keeping it short of a 5.

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 dense sentences with the payload description front-loaded and the sibling routing plus coverage caveat trailing. Every clause carries information; none is filler.

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 must describe returns, and it does so thoroughly (signals, quotes, pin cites, parentheticals plus flag colors). Combined with the stated citer-coverage limit, an agent has everything needed to call it and interpret results.

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 schema already documents citation, case_name, cluster_id, max_citers, and flag_filter. The description only reinforces the flag-color filtering, adding no syntax or resolution detail beyond the schema, which matches the baseline-3 rule when structured fields do the heavy lifting.

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?

States a specific verb and resource ('Full citator list: every ranked case citing this one') and enumerates the exact payload (parentheticals, verbatim quotes, pin cites, Bluebook signals). It is clearly distinguishable from get_treatment, which is named as the sibling for a different job.

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?

Explicitly states when to use it ('Best for FINDING SUPPORTING AUTHORITY and parentheticals') and when not to ('for comprehensive negative-treatment checking use get_treatment'). It also discloses the coverage boundary (only each case's ~50 top-ranked citers), which is exactly the kind of routing caveat an agent needs.

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