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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context by specifying that the tool returns rule-engine diagnoses about how the element exhibited the issue, going beyond just 'list diagnoses'.

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 and stays reasonably compact. It is slightly wordy with phrases like 'reported as exhibiting one issue in one report,' but it avoids redundant detail and is structured to present the core purpose first.

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 rich parameter schema, output schema, and safety annotations, most information needed to invoke the tool is present. The main gap is the lack of explicit relationship to sibling tools, but the description still conveys the precise scope of the lookup.

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%, with all four parameters documented and given examples. The tool description does not add parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 names a specific resource (one element in one report exhibiting one issue) and explains the focus of the tool: providing diagnoses from rule engines. It is clear enough to distinguish from siblings like listReports and listViolators, though the verb 'provide details' is somewhat generic.

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 implies this is a drill-down tool for a specific existing report, issue, and catalog element, but it does not explicitly state when to use it over siblings like listIssues or listViolators, nor does it give exclusion criteria. Usage is inferable but not directly stated.

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