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

Annotations already establish this as read-only, idempotent, and non-destructive, lowering the bar. The description adds useful return-content context, but it does not disclose behavior around partial matches, multiple judges with the same name, or unavailable data.

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 two concise sentences with the action and lookup keys front-loaded. There is no filler or redundant restatement.

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 simple one-parameter lookup with strong annotations and clear schema coverage, the description provides the essential invocation contract and summarizes the return payload. It could mention match/disambiguation behavior, but nothing critical to calling the tool is missing.

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?

The input schema fully documents the single parameter as a full or partial name or numeric person ID, so the description adds little beyond that. The description does clarify that the person ID is a CourtListener ID, which provides helpful source context.

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 uses a specific verb ('Look up') and identifies a clear resource ('judge profile'), along with the lookup keys and returned fields. It is easily distinguished from sibling court tools like court_case_search, court_docket_lookup, and court_opinion_search.

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 clearly implies when to use this tool: whenever a judge's positions, education, or bench history is needed, and by name or CourtListener person ID. It does not explicitly name alternatives or exclusions, but no sibling tool covers judge profiles, so the usage context is unambiguous.

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