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

Annotations already declare destructiveHint=true, readOnly=false and non-idempotent, so the mutate/replace nature is covered structurally. The description nonetheless adds substantial context: it lands as a new version with the prior version retained and restorable, is never a silent no-op, and stays in review rather than publishing. That is meaningful added value beyond the annotations, but it stops short of documenting auth/permission requirements or the size/rate profile of generation work.

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?

The core purpose is front-loaded in the first clause, followed by outcome and edge-case handling. It is dense and leans on long parenthetical asides and em-dash chains, so it reads as slightly rambling even though nearly every sentence carries distinct information.

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 and a complex nested-object schema, the description carries the burden well: it covers the outcome (new version, old restorable), the no-op guard, failure handling for unfulfillable requests, approval/publish boundaries, and the inline-vs-async return behavior with a pointer to get_post. An agent has what it needs to call this 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 description coverage is 100%, so the schema already documents every parameter including the nested review object and the verbose flag. The description's scoping discussion of `note` (classified into caption / one slide / all media / timing) adds meaning about how the input is interpreted, but the per-field mechanics are already covered.

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 (asks for changes to a post, from a plain-language note) and anchors it to a known UI affordance. It explicitly names the sibling it is not: 'For a post whose whole idea is wrong ... use remake_post instead,' so an agent can distinguish the two 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 explicit when-to-use (one scoped change) versus when-not (whole idea wrong → remake_post), plus routing for approved/scheduled posts (needs a fresh approve_post). It also explains what happens when the request can't be fulfilled and which sub-cases fail instantly.

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