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

Beyond the readOnly/idempotent annotations, it discloses the key behavioral trait: the content is an immutable snapshot frozen at write time, not live state, and is byte-for-byte identical to what the team reads. That immutability and staleness caveat is exactly the context annotations cannot express, and it directly prevents a misreport of a stale finding.

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?

Leads with what the tool returns, then the staleness caveat, then parameter and quoting rules — good front-loading with no filler sentences. It is dense and slightly clause-heavy in the opening sentence, which costs a point but not clarity.

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?

There is no output schema, so the description carries the return-value burden and does: it states the response is the full report text with frozen inline numbers. Combined with the immutability and staleness guidance, an agent has everything needed to call it and interpret the result correctly.

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 coverage is 100%, and the description's parameter-relevant content (snapshot is 1-based and defaults to latest; report_id comes from the list tools) largely restates what the schema and the report_id description already say. It adds interpretive framing about older snapshots but no new format or constraint details, so baseline 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 full text of one report" is a specific verb+resource, and the description immediately qualifies it as "a dated, immutable snapshot" with numbers frozen at write time. That framing distinguishes it from list_reports (index/listing) and from the mutable list tools an agent might otherwise reach for.

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?

Gives explicit when-to-use (quote the document the team sees), a when-not/verify step ("check the current state with the list tools before calling a finding open"), and a phrasing rule for archived subjects (past tense). It also names the concrete alternative tools by role, leaving little to inference.

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