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

The description adds valuable behavioral context beyond the readOnlyHint and openWorldHint annotations: it states that results are structured summaries with source provenance and that omitted fields should not be interpreted as defaults or negatives. This is especially important without an output schema and directly supplements the openWorldHint=false annotation.

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: it opens with the core action, then lists use cases, then closes with an essential interpretation caveat. Every sentence earns its place, and no filler is present.

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?

Given the 9-parameter schema, no output schema, and the need to guide an agent, the description is largely complete: it defines the domain, the use cases, the return shape, and the interpretation caveat. It could be slightly stronger with an explicit note about pagination or the 'active source documents' distinction, but the schema and description together cover nearly everything needed.

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 documentation already carries the burden for parameter meaning. The description does not add parameter-specific semantics, but it does not need to; the schema descriptions for q, limit, case_type, judge_slug, and the other filters are already detailed.

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 verb (search), the resource (extracted court filing rules from active source documents), and a specific list of topics covered. It does not explicitly call out sibling tools like get_judge_rules, so differentiation is implicit rather than explicit.

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 gives strong context for when to use the tool with a detailed list of use cases: e-filing requirements, service, timing, fees, courtesy copies, rejection windows, and judge preferences. It does not mention alternatives or exclusions, so there is no explicit when-not-to-use guidance.

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