delete_post

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

Description merely repeats the action 'Delete' without adding context beyond what annotations already provide (destructiveHint). Does not mention irreversibility, associated data impact, or permission requirements.

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?

Extremely concise with no wasted words. However, slightly under-specified for a destructive action. Efficient but could benefit from a sentence on consequences.

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?

Given the simplicity (one parameter, no output schema), the description is adequate but lacks details on permanence, cascading effects, or idempotency behavior beyond the annotation hint.

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?

Single parameter 'postId' is fully described in the schema with 'The post ID to delete'. Description adds no additional meaning. Schema coverage is 100%, baseline of 3 applies.

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?

Description clearly states the verb (Delete), resource (a post), and identifier (by its ID). Distinguishes effectively from sibling tools like update_post, get_post, and list_posts.

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?

No explicit guidance on when to use this tool vs alternatives. However, the purpose is self-evident for a delete operation. Lacks when-not-to-use or prerequisite information.

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