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

With no annotations, the description carries the full burden. It does disclose meaningful traits — the finding is public and immutable, and removed/private content is unavailable — which is real behavioral context. It stops short of explaining auth requirements, what the attachment actually returns, or pagination/size behavior.

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 short sentences with the resource scope front-loaded, which is efficient. The second sentence is compact to the point of being cryptic, forcing the agent to interpret what 'external truth' means rather than stating the caveat plainly.

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?

A read tool with no output schema, no annotations, and an undocumented required parameter leaves significant gaps: the agent does not know what a 'finding attachment' contains or how postId is obtained. The description covers immutability but not the calling prerequisites.

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% and the single parameter postId is entirely undocumented in the schema (only a regex pattern). The description never mentions the identifier or its expected format, so it fails to compensate for the coverage gap.

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) and resource (finding attachment), qualified as 'public immutable', so the agent understands the scope. However, it does not distinguish itself from the sibling tools check_finding and preview_finding, which appear to operate on the same domain object.

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?

There is no explicit when-to-use guidance and no mention of the tightly related siblings check_finding or preview_finding. The cryptic clause 'checked supplied results are not external truth' gestures at a relationship to checking but never states when to choose this tool over those alternatives.

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