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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered without the description. The description adds no behavioral context beyond that — it doesn't say what happens on an invalid ID, whether the record is cached, or anything about the cryptic 'court report offer'.

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?

It is a single short sentence with zero padding, which is good, but it is a sentence fragment that leads with content rather than the action. Brevity here edges toward under-specification rather than effective conciseness.

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 one-parameter read tool with full annotation coverage and a fully documented schema, the description is minimally adequate, and it does partially compensate for the absent output schema by naming returned fields. However, it never states the operation itself, so an agent must infer the core purpose from the tool name.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains that the id comes from search and its valid range. The description contributes nothing additional about the parameter, so the baseline of 3 applies.

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 is a noun phrase listing returned fields ('name, state and address') rather than stating a verb+resource, so it never explicitly says it fetches a single court by ID. It does convey the resource and its scope (one court), which is more informative than a pure restatement of the title, but it offers no differentiation from siblings like get_attorney or get_judge.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as search or the other get_* tools. The only usage cue (the ID coming from search) lives in the schema, not the description.

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