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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds useful behavioral context by scoping to public cases, noting fields are 'as shown on the case page,' and qualifying disposition as 'when recorded.' This goes beyond the structured annotations without contradicting them.

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 immediately states the action and input, then compactly lists the returned fields. Every part earns its place, and there is no filler or redundant qualification.

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 read-only tool with no output schema, the description is complete: it specifies the input format, the source of the data, and the full set of returned fields, including the conditional disposition. The annotations cover safety and idempotency, so nothing critical 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?

Schema description coverage is 100% and the single case_url parameter already includes a full example and notes that it is returned as canonical_url by search_cases and get_company_cases. The tool description restates the URL requirement but adds no new parameter semantics beyond what the schema provides.

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 opens with a specific verb and resource: 'Get a public case by its Docket Nexus URL.' It also enumerates the exact fields returned (caption, court, docket number, dates, judge, cause, nature of suit, parties, disposition), which clearly distinguishes this case-detail tool from siblings like get_case_docket and search_cases.

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 makes the intended usage context clear: call this when you already have a Docket Nexus case URL and want the case summary page data. It does not explicitly name alternatives or exclusions, but the URL-based precondition and field list are sufficient directional guidance.

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