Delete post

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

With no annotations, the description carries the responsibility for behavioral disclosure. It reveals the conditional scope of deletion (draft/scheduled only) and that published posts are untouched, which is valuable. However, it omits other behavioral traits such as irreversibility, permission requirements, or side effects on associated data.

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 a single, efficient sentence that leads with the verb 'Delete' and adds only a necessary scoping qualification. Every word earns its place and there is no redundancy.

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 tool with one parameter and no output schema, the description supplies the key contextual information: what can be deleted (draft/scheduled) and what cannot (published). It lacks a brief note on effects (e.g., confirmation, permanence) but is otherwise sufficient for correct invocation.

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?

There is only one parameter (postId) and schema description coverage is 0%, so the description must compensate. It adds meaning by restricting the post to be in draft or scheduled status, which informs what postId should reference. Still, it does not explicitly define postId or explain where to obtain it, though the tool name and single-parameter schema make this largely unambiguous.

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 states the specific verb 'Delete', the resource 'post', and the scope 'draft/scheduled', while explicitly excluding published posts. This clearly distinguishes it from sibling tools like delete_comment or delete_media and clarifies that it does not affect published content.

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 implicitly provides when-to-use by restricting to draft/scheduled posts and when-not-to-use by stating published posts are kept. However, it does not name an alternative tool for deleting or unpublishing published posts, leaving that routing to the agent's inference.

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