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

Annotations already declare readOnlyHint/destructiveHint=false, so safety is covered; the description adds real value beyond that by disclosing the returned payload shape (stable mediaLink, refused request, dashboard-worded status) and the semantic that 'reading a post never approves it,' clarifying the read/approve workflow boundary. It could add more on pagination/size limits beyond the verbose note.

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?

Purpose and the key when-to-use/alternative routing are front-loaded in the opening sentences, and the verbose note is sensibly placed last. The middle enumeration of returned fields is dense but each item is informative; slightly long but not padded.

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 return-value burden and does so by listing the major fields and the verbose variant. Combined with full schema coverage and read-only annotations, an agent has what it needs to call correctly; only large-response handling is left implicit.

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 100%, so all four parameters are already documented — the baseline is 3. The description reinforces verbose (full stored record: brief, image prompt, version history) but does not add syntax or constraints the schema lacks, so no credit above baseline.

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 then enumerates the concrete payload — caption, slide list with mediaLink, scene plan, last change, status. It explicitly distinguishes itself from list_posts ('only returns a headline'), so an agent can route 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?

Gives an explicit when-to-use ('review or critique what Rebbel actually wrote before approving it') and names the alternative plus its limitation ('list_posts only returns a headline, which isn't enough to judge copy against a brand's voice'). The condition that selects this tool is unambiguous.

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