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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral context beyond annotations by specifying that the graph walk is forward-only, restricted to in-corpus cases, and that results represent the precedents relied upon by the given judgment. This is meaningful additional transparency.

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 compact and front-loaded: the first sentence states exactly what the tool does, the second clarifies the relationship with a sibling, and the final sentence gives a practical usage heuristic. Every sentence earns its place, with no filler or repetition.

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 read-only listing tool with an output schema and strong annotations, the description covers the tool's purpose, direction, scope boundary (in-corpus), relationship to sibling tools, and a concrete use case. Pagination details are handled by the input schema defaults and constraints, so nothing essential is missing for correct invocation.

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 only 25%, with only case_id documented in the schema. The description provides no additional meaning for limit, offset, or response_format, and it does not compensate for the low schema coverage. The parameters are reasonably self-descriptive, but the description itself adds no semantic value beyond the schema.

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 ('Walk the citation graph FORWARD: list the in-corpus cases that THIS judgment cites') and explicitly differentiates from caselaw_get_cited_by, which is the sibling that lists cases citing this judgment. The directionality is unambiguous, so an agent can select it correctly without guessing.

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 explicitly says to combine with caselaw_get_cited_by to traverse precedent backward and forward, and it gives a concrete usage scenario ('Most useful on RECENT judgments'). This is clear, actionable guidance that names the complementary alternative and explains when the tool provides the most value.

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