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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true; the description earns credit for adding that an approval link is returned and that GBPly's post policy check still applies, which explains why the call is not immediately effective. It does not say what happens to fields omitted from the new content or how the approval is later tracked (e.g. get_request_status).

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?

Three short sentences, front-loaded with the action, then the payload rule, then the return value and policy caveat. No filler.

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?

For a 14-parameter, non-idempotent mutation with no output schema and low schema coverage, the description covers the core contract (full content, approval link, policy check) but is thin on the many event/offer-specific fields and on how the pending request is later polled or resolved.

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 only 36% across 14 parameters, so the description must compensate. Beyond 'send the full new content' it says nothing about post_type, cta_type/cta_url pairing, coupon_code, terms_conditions or the event_* fields, leaving most of the parameter surface undocumented.

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 ('ask the user to approve changes to an existing post') and scopes it to published, scheduled or draft posts. This cleanly separates it from siblings request_create_post and request_delete_post without needing to name them.

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?

The phrase 'changes to an existing post' clearly establishes the edit-existing use case, and 'Send the full new content' tells the agent to supply a complete replacement rather than a delta. It stops short of explicitly naming request_create_post/request_delete_post as the alternatives or stating when not to use it, so a 4 rather than a 5.

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