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

While annotations already declare readOnlyHint=true and destructiveHint=false, the description adds a crucial behavioral detail: measured cases appear only after claim-specific publication authorization. This goes beyond the annotations by explaining a condition that affects the results. It does not contradict the annotations, and it provides meaningful context about the tool's behavior without over-explaining.

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 sentences with zero fluff. The main purpose is front-loaded in the first sentence, and the second sentence adds a precise nuance without wasted words. Every word earns its place, making it highly efficient for an agent to parse quickly.

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 only two optional parameters, an output schema, and annotations covering safety, the description is complete enough. It states what is listed, includes a key authorization condition, and relies on the output schema for return details. No additional information is needed for an agent to correctly invoke this tool.

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 already provides 100% coverage for both parameters (limit and niche) with clear descriptions. The tool description does not add any additional parameter-specific meaning or interaction details. Since the schema covers the parameters fully, the baseline of 3 is appropriate; no extra value is contributed by the description.

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 tool 'lists governed public reviews, operating evidence, and illustrative context' which is a specific verb-resource pair, and the nuance about measured cases distinguishes it from generic list tools. It is not tautological and clearly identifies the resource as public proof evidence, differentiating it from sibling list tools like list_benchmarks or list_resources without needing to open the schema.

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 does not explicitly mention when to use this tool versus alternatives. It provides a behavioral constraint about authorization for measured cases, which offers some context on when cases appear, but there is no explicit 'use this for X, use that for Y' guidance. The intended usage is implied by the resource type but not contrasted with siblings.

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