Delete a post

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

Beyond the annotations (destructiveHint: true, idempotentHint: false), the description discloses two important consequences: the action cannot be undone and the post may persist in existing feeds and caches. It also reiterates the hard requirement that confirm must be true, reinforcing the safety gate.

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 filler. It front-loads the core action, then packs irreversibility, cache/feed caveat, and the confirm requirement into the second sentence.

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 delete operation without an output schema, the description covers the key operational facts: scope, irreversibility, residual visibility in feeds/caches, and the required confirmation. No critical detail an agent needs before invoking it is missing.

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 parameters are already well documented. The description adds the ownership constraint on 'uri' (your own posts) and reinforces the confirm flag, but doesn't introduce new parameter semantics beyond that.

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 opens with 'Delete one of your own posts,' naming a specific verb, resource, and an ownership constraint. This clearly distinguishes it from sibling tools like unlike_post or unrepost, which remove interactions rather than the post itself.

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 'one of your own posts' provides immediate context that this tool is only for deleting posts owned by the user, not for removing other users' content. It doesn't explicitly name alternative tools, but there is no competing deletion tool among the siblings, so the usage context is clear.

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