Delete a post

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

No annotations are provided, so the description carries the full burden. It usefully discloses that deletion happens 'through SDUI' and that it includes a verification step. However, it omits consequences of failure, permanence of deletion, and any authorization requirements—context an agent would benefit from.

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?

A single concise sentence front-loads the action and adds two meaningful details (SDUI channel and feed verification) without any redundant padding. Every word earns its place.

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 one-parameter tool, the description covers the primary action and a notable verification behavior. It leaves gaps around the meaning of 'SDUI,' behavior when the post does not exist, and what the tool returns or reports—missing information for a fully autonomous agent.

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 has one postId string with 0% description coverage, and the description does not mention the parameter. Although 'postId' is self-explanatory in the context of 'deletes a post,' the description adds no meaning about its format, source, or constraints, leaving the schema to do all the work.

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 a specific verb and resource ('deletes a post') and adds extra precision with 'through SDUI' and 'verifies it no longer appears in the feed.' It does not explicitly name sibling alternatives, but the combination of post and feed distinguishes it from related tools like delete_ghost_entry.

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 guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites. The intended usage is implied by the action itself, but the description does not help route an agent away from similar deletion tools.

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