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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond them: "reading a post never approves it" (important given the many approve_*/review_post siblings) and the size/side-effect profile of verbose. It stops short of permissions or rate-limit detail, but for a read-only fetch that is a minor gap.

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 core action and the routing signal, then details. It is a long paragraph, but since no output schema exists the return-field enumeration is largely load-bearing rather than filler; the dense field list costs some scannability.

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?

With no output schema, the description carries the full burden of describing the return value and does so thoroughly, field by field, including the `ask` concept. All three required ids are accounted for and the verbose mode is explained, so nothing an agent needs to call it 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?

Schema coverage is 100%, so the baseline is 3. The description goes slightly beyond the schema by naming what the verbose record actually contains ("brief, image prompt, version history"), which concretely helps an agent decide whether to pass verbose:true; the other three params are adequately documented in the schema itself.

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 ("Reads one post") and enumerates exactly what that read returns: caption/alternates, media with per-image text and mediaLink, scene plan, status, and `ask`. It also distinguishes itself from the sibling list_posts, so an agent can pick it without opening either schema.

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?

Explicitly names the condition for use ("review or critique what Rebbel actually wrote before approving it") and the alternative it supersedes (list_posts "only returns a headline, which isn't enough to judge copy against a brand's voice"). That is a clear when-to-use plus a when-to-use-something-else.

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