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

With no annotations provided, the description must carry the behavioral burden. It transparently states what is retrieved and lists the output components, which covers the tool's read-oriented behavior. However, it does not mention any permissions, latency, error conditions, or limitations – areas that remain opaque for a tool with zero annotation coverage.

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, well-structured sentence that front-loads the core action and resource before enumerating components in a colon-separated list. It is concise without losing substance, though slightly longer than strictly necessary.

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 tool has no output schema, the description compensates by listing the key output elements (executive holding, practice pointer, cross-border matrix, judge analytics). It gives the agent a solid expectation of what will be returned. It does not detail data format or interpretation, but for a single-parameter retrieval tool this is largely sufficient.

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 coverage is 100% and the schema already gives detailed examples for case_number. The description adds no parameter-specific meaning beyond the context 'specific European patent case', which is consistent but not additive. Baseline 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 opens with a specific verb ('Retrieve') and a clear resource ('comprehensive strategic docket intelligence') for a defined scope ('specific European patent case'), then enumerates the deliverables. This distinguishes it from siblings like search_european_dockets (search vs. specific case) and get_judge_benchmarks (subset of the analytics).

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 phrase 'for a specific European patent case' clearly implies the tool is for when the agent already has a case number, not for discovery. Context signals and sibling names reinforce this, but the description does not explicitly name alternatives or conditions. Clear context, no exclusions.

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