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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds valuable behavioral context: it explicitly states the authentication requirement (X-API-Key header), the rate limit (50 req/day shared with data.ungovr.org), and how to obtain a key. This goes beyond the annotations without contradicting them, providing critical operational details for correct invocation.

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?

Two sentences with no fluff. The main purpose is front-loaded, followed by essential operational requirements. Every sentence earns its place—no redundant information or filler.

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 detail-retrieval tool with one parameter and no output schema, the description provides the necessary invocation context: purpose, required input, authentication, and rate limit. It even hints at the response contents (findings, recommendations, responses). While it doesn't specify the exact return format, this is minor for such a straightforward tool and the description is otherwise complete.

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 covers the single parameter 'id' with a clear description ('Report ID (from search results)'), achieving 100% coverage. The description does not add any additional semantic detail about the parameter format or constraints, so it adds no value beyond the schema. Baseline 3 is appropriate.

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 action ('Get full details'), the specific resource ('a specific California Grand Jury report by ID'), and what content is expected ('findings, recommendations, and responses'). It is distinct from siblings like search_cgj_reports, which retrieves a list based on criteria, and get_entity, which targets a different resource type.

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 that this tool is used when you have a report ID, and the schema clarifies the ID comes from search results. It does not explicitly state 'use search_cgj_reports first to obtain an ID,' nor does it contrast with alternatives, but the implied workflow is clear enough for an agent to understand when to call this tool.

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