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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered. The description still adds meaningful context beyond them: irreversibility, per-network variability in support, and a required human-confirmation step before invocation.

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 core action and its scope, then the destructive caveat, then the confirmation directive. 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 no-output-schema mutation whose annotations carry the safety flags, the description covers irreversibility, network-dependence, and required confirmation. The main gap is that postId's format/derivation is undocumented for a required parameter.

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 50%: idempotencyKey is well documented in the schema, but postId has no description anywhere. The description adds nothing about what postId expects or how to obtain it, leaving half the parameters 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+resource and scopes it: 'Remove an already published post FROM THE SOCIAL NETWORK,' which separates it from unschedule_post (not yet live) and arguably from delete_post. It does not name those siblings, so the boundary with delete_post is left for the agent to infer from scope wording alone.

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 precondition ('Ask the human before using it') and a conditional caveat ('not every network allows it'), which is real routing guidance. It stops short of naming the alternative tool to use when the post is unpublished or when the network refuses the action.

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