Remove a post from a content item. The post survives on its own channel and keeps its schedule, text, status, and tags. Only the link to the content item goes away. To delete a post, call deletePost. A second call with a post that belongs to no content item changes nothing, and the mutation reports success.

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the bar is lower; the description still adds real context: what survives vs. what is removed, that a redundant call is a silent no-op reporting success, that explicit confirmation is required, and that provider errors are failures even with HTTP 200. The only caveat is that the no-op success wording sits in mild tension with idempotentHint=false, though it describes a single case rather than a general claim.

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 behavioral content is front-loaded and each sentence carries information, but roughly the entire first paragraph is duplicated from the title, and the trailing sentence ('Current Buffer GraphQL removePostFromContentItem ...') reads as generic template boilerplate. That redundancy costs the definition real conciseness.

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 destructive, 7-parameter mutation with nested payload and no output schema, the description covers the mutation's effect, the destructive scope, the alternative tool, the no-op edge case, confirmation, and error semantics. The main gap is that no return-value description is given, though the 'reports success' wording partially covers the no-op case.

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 id, postId, fields, account, confirm, payload, and payload_file in detail. The description adds only two loose hints ('Requires explicit confirmation' and 'Use upstream fields to bound data'), which the schema already conveys more precisely, so the baseline 3 applies.

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 ('Remove a post from a content item') and spells out the exact effect ('the post survives ... only the link ... goes away'), which meaningfully distinguishes it from delete_post and add_post_to_content_item. However, the text is a verbatim duplicate of the title, so it adds less differentiation than its length suggests.

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 routing to the alternative ('To delete a post, call deletePost') and clarifies the edge case where a post belongs to no content item. It stops short of stating prerequisites or when-not-to-use beyond that single alternative.

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