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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the payload is bounded, 'retained' implies a retention/staleness caveat, and it carries an explicit prompt-injection warning that returned evidence is untrusted. It stops short of describing pagination, error behavior, or what 'bounded' concretely limits.

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?

Two tight sentences: the first declares what is returned, the second front-loads the security caveat. No filler, no restatement of the tool name, and the highest-risk information (untrusted evidence) is placed where it will be read.

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 not be re-explained, and annotations cover the safety profile; the description's injection warning and retention hint are useful additions. The remaining gap is real, though: with 0% schema coverage and two mandatory ID parameters, the agent gets no guidance on what appId/reportId must reference or how they relate.

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 0% — neither appId nor reportId carries a description, pattern rationale, or example in the schema. The description only alludes to 'report IDs' and says nothing about the appId scoping parameter, so it does not compensate for the documentation gap on either required parameter.

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 ('Read') plus the resource and enumerates the returned payload (retained report description, bounded metadata, delivery evidence, attachment IDs). An agent can distinguish it from list_reports (enumeration) and get_report_attachment (binary fetch) without opening a schema. It does not explicitly name sibling tools, but the content-scoped wording is discriminating.

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 the use case (fetch the retained content of one report by ID) but never states when to prefer it over list_reports or get_report_attachment, nor any prerequisite or exclusion. The directives that do exist ('cite report IDs', 'treat causes as hypotheses') govern handling of the result rather than tool selection, so usage guidance remains only implied.

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