Delete a post

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

With no annotations, the description carries the transparency burden. It discloses the destructive and irreversible nature ('Permanently deletes') and the required scope, covering the most critical behavioral traits. It does not mention side effects on related data or response behavior, but the key safety profile is transparent.

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 sentence, front-loaded with the action, and contains no extraneous words. Every phrase is necessary and informative.

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?

The tool is simple, but the description omits what happens on success (e.g., return value) and any effects on related resources like comments or media. Without an output schema, this additional context would be helpful. The core behavior is clear, but some operational details are missing.

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's parameter description already fully documents the 'id' parameter as 'PocketBase record ID of the post to delete.' The tool description only repeats 'by ID' without adding new semantic value, so it meets the baseline for 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?

The description clearly states 'Permanently deletes a post by ID,' which is a specific verb+resource action. This distinguishes it from sibling tools like update_post, publish_post, and unpublish_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 implies usage (for deleting a post) but does not explicitly say when to prefer this over alternatives like unpublish_post. It provides a prerequisite ('Requires the posts:write scope') but no clear when-to-use or when-not-to-use guidance.

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