delete_posts

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool deletes posts, implying a destructive mutation, but doesn't mention permissions required, whether deletions are permanent or reversible, error handling, or any rate limits. This leaves critical behavioral traits unspecified for a destructive operation.

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, efficient sentence with no wasted words, making it appropriately concise. However, it's overly brief given the tool's destructive nature and lack of other documentation, which could be seen as under-specification rather than ideal conciseness.

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 destructive nature, no annotations, no output schema, and 0% schema coverage, the description is incomplete. It doesn't explain what happens after deletion, return values, error conditions, or how it interacts with sibling tools. More context is needed for safe and effective use.

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?

Schema description coverage is 0%, meaning parameters are undocumented in the schema. The description adds no information about the 'deletions' parameter, such as what it contains, how to structure deletions, or examples of usage. It fails to compensate for the lack of schema documentation, leaving parameters semantically unclear.

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 'Delete posts from entities' clearly states the action (delete) and target (posts from entities), which is better than a tautology. However, it doesn't specify what 'entities' are or differentiate this tool from sibling tools like 'delete_entities' or 'update_posts', leaving the scope somewhat vague.

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 provides no guidance on when to use this tool versus alternatives like 'delete_entities' (which might delete entire entities) or 'update_posts' (which might modify posts instead). There's no mention of prerequisites, constraints, or typical use cases, offering minimal context for selection.

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