delete_post

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

With no annotations provided, the description carries the full behavioral burden. It discloses two key traits: deletion is permanent and ownership is required. However, it does not mention potential consequences like cascading effects or error responses, which are relevant for a destructive tool. The core behaviors are covered, though not exhaustively.

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, concise sentence with no wasted words. 'Permanently' and 'you own' are essential qualifiers that add value, and the structure is front-loaded with the action verb. It is a model of brevity.

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 tool's simplicity—one parameter, no output schema, no annotations—the description provides the essential action but leaves out important context such as the meaning of the 'id' parameter and success/failure behavior. It is minimally viable but not fully complete.

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 input schema defines only an 'id' parameter with no description, and the description does not mention it. Since schema coverage is 0%, the description should clarify that 'id' refers to the post being deleted, but it remains implicit. This creates a gap in parameter understanding.

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 specifies the tool's function: 'Permanently delete a post you own.' The verb 'delete' and resource 'post' make the action explicit, and the qualifier 'you own' distinguishes it from sibling tools like list_posts or update_post. This fully captures the tool's unique purpose.

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 implies usage context—use when you own a post and want to permanently remove it—but does not explicitly mention alternatives or exclusions. There is no guidance such as 'use update_post to modify instead' or 'do not use for posts you don't own,' leaving the decision-making to inference.

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