post_delete

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

The description adds crucial behavioral details beyond annotations: it explains the default non-destructive behavior for platforms and the optional destructive action, which is consistent with destructiveHint=true and provides necessary nuance.

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 extremely concise—only two sentences—with no wasted words. It front-loads the primary action and follows with the key conditional behavior.

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 tool with only two parameters and no output schema, the description covers all necessary information: the deletion action, the default scope, and the optional extended behavior. It is complete and sufficient.

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?

While schema coverage is 100%, the description adds value by explaining the default behavior of the delete_on_platform parameter and its effect, making the tool usage clearer.

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 it deletes a post from the database and distinguishes the default behavior (no platform removal) from the optional platform deletion. It is specific and contrasts with sibling tools like post_delete_on_platform.

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 description explains when to use the optional delete_on_platform parameter, providing clear context. However, it does not explicitly compare with the sibling tool post_delete_on_platform, though the distinction is implied.

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