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

No annotations are provided, so the description must carry the full burden. It discloses that the tool returns 'source-linked' rules and can be filtered by topics, but it does not state whether the operation is read-only, destructive, requires authentication, or has rate limits. The description is adequate but not rich.

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 that states the core purpose first, then adds an optional filtering note. Every word earns its place; no extraneous details.

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 input schema is fully covered and there is no output schema, the description should explain return format or structure. It mentions 'source-linked' but does not describe what the output contains (e.g., a list of rules, formatted text, structured data). Without output schema, this is a gap. Overall, the description is adequate for a simple retrieval tool but lacks completeness on return values.

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%, meaning the schema already describes both parameters well. The description adds value by explaining the optional 'topics' parameter with concrete examples (PowerPoint, video, demonstratives), which clarifies permissible filter values beyond the schema's generic 'Optional presentation topics to filter'. The 'judge_slug' parameter is tied to the sibling tool find_judges, hinted by the description's mention of 'Canonical slug returned by find_judges' in 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 clearly specifies the verb 'Get' and the resource 'source-linked courtroom technology and presentation rules for a judge'. It also lists example topics, which distinguishes it from siblings like get_judge_biography or get_judge_profile. However, it does not explicitly differentiate from get_recent_rule_changes, which might overlap in scope.

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 when to use this tool (to get rules for a judge, optionally filtered by topics) but provides no guidance on when NOT to use it or explicit alternatives among siblings. For instance, it doesn't mention get_recent_rule_changes as an alternative for just checking recent updates.

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