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

Goes well past the annotations: it discloses that redaction is an entitlement limit rather than an empty result, that severity remains accurate while text fields become '[redacted]', and that the transcript is adversarial content requiring [UNTRUSTED:<id>] fencing. It also states the required read scope, which the readOnlyHint alone does not convey.

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?

Front-loads what is returned, then the redaction edge case, then the labeled SAFETY block — good ordering with no filler. The redaction sentence is long and packs several facts, which keeps it from being maximally scannable, but every clause carries real information.

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?

An output schema exists so return values need no explanation, and the description still covers the two things that could mislead an agent: entitlement-based redaction and untrusted-content handling. Nothing needed to call this correctly on a security tool is missing.

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 single finding_id parameter has 0% schema description coverage and the description never explains its format or origin (e.g., obtained from list_findings). The name is self-explanatory enough that this is a minor gap rather than a blocking one.

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?

States a specific verb and resource ('Fetch one finding in full') and enumerates exactly what comes back (technique, severity, status, attack transcript), which cleanly separates it from the list_findings sibling. An agent knows immediately this is the single-record detail call.

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?

Frames the use case explicitly ('so you can diagnose and fix the vulnerability') and, importantly, tells the agent that retrying will not change a redacted result — a real usage constraint. It does not, however, name list_findings as the alternative for browsing or say where a finding_id comes from.

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