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

With no annotations provided, the description carries full burden. It discloses the ranking order and descending sort, which is key behavior, but does not mention read-only status, output format, or any rate limits. For a simple read-only query, this is adequate but lacks extra context.

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, front-loaded sentence with no wasted words. It states the action, subject, ordering rule, and usage context efficiently.

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?

This is a simple tool with one optional parameter and no output schema. The description covers the essential ranking logic and usage scenarios. It does not detail the return structure, but the tool name and context imply it returns judge objects. It is reasonably complete for a tool of this complexity.

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 0%, so the description must compensate. The phrase 'top-N' implicitly explains the limit parameter's meaning, connecting the numeric limit to the number of judges returned. The schema provides default/min/max, and the description adds semantic clarity around the parameter's role.

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 clearly states the tool returns the top-N California judges ranked by CJP discipline severity, with an explicit ordering hierarchy (removal > censure > admonishment). This specific verb and resource distinguish it from sibling search tools like search_judges and other 'top' tools (top_das, top_officers).

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 'Use for "worst judge" / "most-disciplined judge" / ranking questions,' giving clear when-to-use guidance. It does not explicitly mention alternatives or when not to use it, but the ranking use case is clearly delineated.

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