delete_post

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

The description notes the deletion is permanent, a key behavioral trait. However, no annotations are provided, and it does not disclose other behaviors like authentication requirements, side effects on replies, or error handling.

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, front-loaded sentence that efficiently conveys the action and permanence. Every word adds value; 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 1-parameter delete tool, the description covers the core action and permanence. However, it omits details like the need for the post to exist, what happens on failure, or whether it supports batch operations. With no output schema, agents lack return value expectations.

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 single parameter 'uri' has no description in the schema (0% coverage) and the tool description adds no explanation. The agent is left to infer that URI is the post's identifier without any guidance on format or source.

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 states the tool deletes a post on AT Protocol, specifying it permanently removes it. This verb+resource combination is distinct from sibling tools like create_post or like_post.

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 gives no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. Usage is implied but not explicitly contextualized.

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