delete_post

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

Adds detail beyond the annotations: irreversibility warning, idempotent no-op behavior, auth requirements, ownership restriction, and the fact that the post id remains. This enriches behavioral understanding and aligns with the annotations (destructiveHint=true, idempotentHint=true).

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?

Every sentence earns its place: main action, safety characteristics, prerequisites, scope, alternative, and warning. The description is dense but not redundant, and the core action is front-loaded.

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 one-parameter delete operation, the description covers purpose, safety, idempotency, auth, ownership, irreversibility, and differentiation from the comment-deletion sibling. Combined with strong annotations, no critical gap remains.

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?

The schema already documents thing_id thoroughly, including accepted formats and the automated t3_ prefix. The description adds no parameter-specific semantics beyond referencing 'the post you name,' so baseline 3 applies due to high schema coverage.

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 the exact action: 'Permanently delete one of your own posts.' It uses a specific verb+resource, and differentiates from sibling delete_comment by explicitly noting 'use delete_comment for comments.'

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?

Provides clear when-to-use guidance: works only on self-authored posts, requires credentials, and excludes comments with an explicit alternative. This tells the agent both the prerequisites and the boundary of applicability.

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