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 non-obvious behavior: the signed link is short-lived and must be re-fetched, and results may be partially redacted. It doesn't mention size limits or rate limits, which keeps it from a 5.

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-loaded with the return payload and its components, followed by one short sentence on link expiry. No filler, and the most decision-relevant fact (what you get) comes 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?

The tool is simple (one required param), an output schema exists, and the description still covers the return shape, redaction caveat, and link lifetime. Nothing an agent needs in order to call this correctly 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?

With one parameter at 100% schema description coverage, the schema already explains that attachment_id comes from get_feedback attachments. The description restates that provenance but adds no format, encoding, or validation detail beyond the schema, 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?

States a specific verb and resource ('Returns one image of a feedback item') and immediately scopes it by naming where the id comes from (get_feedback), which separates it from get_feedback and the other siblings. An agent knows exactly what it gets back: preview image content, dimensions, capture location, redaction status, and a full-size link.

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 a clear precondition (attachment id from get_feedback) and an operational rule ('Call again for a fresh link') that tells the agent what to do when a link expires. It stops short of stating when not to use it or naming an alternative path, but for a single-purpose retrieval tool the context is unambiguous.

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