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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the resource scope and the fact that diagnoses come from rule engines, but it does not describe output shape, pagination, or other behavioral details. This is similar to the calibrated mid-tier examples: annotations do the heavy lifting, with modest descriptive value added.

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 sentence that immediately states the action, object, and scope without filler or repetition. It earns every word and is well front-loaded.

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 low-complexity read-only tool with full parameter documentation, a rich output schema, and safety annotations, the description is nearly complete. It only lacks an explicit usage boundary against sibling tools, but that gap is covered under usage guidelines rather than this dimension.

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 has 100% parameter description coverage, so each of the four required parameters is already documented. The tool description only ties them together conceptually rather than adding new field-level meaning, so the baseline of 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 states a specific verb and object: it provides details about a single element, issue, and report, with the distinguishing content being rule-engine diagnoses. This makes its purpose clear and separates it from siblings like listIssues and listViolators.

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 scoped language ('one element', 'one issue', 'one report') implies when this tool is appropriate, but there is no explicit guidance about when to use it instead of sibling tools. An agent must infer the boundary rather than being told it.

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