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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, covering the safety profile. The description adds the nuance of returning 'basics' rather than full details, which is useful but minimal. It does not contradict annotations and provides no additional behavioral context beyond what the annotations and schema already communicate.

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 concise sentence, 'Provide basics about all available reports,' with no filler. It front-loads the action and clearly states the scope. Every word earns its place.

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 zero-parameter list tool with an output schema and strong annotations (readOnly, idempotent, not destructive), the description sufficiently states the tool's purpose. The only gap is lack of explicit usage guidance relative to siblings, but that is minor given the simplicity of the operation and the richness of structured metadata.

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 tool has zero parameters, so there is nothing to document beyond the schema, which is vacuously 100% covered. Per the rubric, a 0-raw tool gets a baseline of 4. The description does not need to explain parameter semantics since there are none.

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 identifies the action ('provide basics') and the resource ('all available reports'), which distinguishes it from sibling tools like getReport (specific report) and listDiagnoses/listIssues listViolators (report subsets). However, it does not explicitly name any sibling or contrast itself, so it misses the top score.

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?

No guidance is given for when to use this tool versus alternatives. The sibling list suggests other report-related tools exist, but the description does not say 'use this to get a summary of all reports' or 'for details, use getReport.' An agent must infer the intended use case without explicit instructions.

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