Delete a published post

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

Annotations already declare destructiveHint true and readOnlyHint false, so the description adds the platform limitation (Instagram/TikTok unsupported) which is beyond the annotation. This is useful behavioral context, and there is no contradiction.

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 description is two sentences with no redundancy. It front-loads the main action and then states a key constraint, making it efficient and easy to parse.

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 simple delete operation with a full schema and output schema, the description is adequate. It could mention permanence, but destructiveHint already conveys that. The platform constraint is the key additional context, and it's provided.

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 100%, so all three parameters are well-documented in the schema. The description adds no new parameter-specific semantics beyond what's already in the schema, so a baseline score of 3 is appropriate.

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?

The description clearly states the tool deletes a published post, using a specific verb and resource. It distinguishes itself from siblings by specifying it applies only to already-published posts, and the platform restriction further differentiates it from other operations.

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?

It implies usage for published posts and explicitly lists unsupported platforms, giving clear context. While it doesn't name alternatives like cancel_scheduled for scheduled posts, the phrase 'already published' effectively guides the agent to use this only for live posts.

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