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 reveals soft-delete semantics, scheduler-side scope (published posts stay LIVE on the platform), the requirement for a typed confirmation that prevents unconfirmed deletion, and per-post failures in the results array. These are meaningful behavioral disclosures beyond the schema.

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 dense yet front-loaded: the core function appears first, followed by the first-call pattern, anti-patterns, and behavioral caveats. Every sentence carries operational value with no filler or repetition.

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 tool with two nested parameters, no output schema, and no annotations, the description provides a complete operational picture: invocation method, side effects, scope, and result reporting. It covers everything an agent needs to call it correctly and avoid common mistakes.

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%, so the description must compensate. It explains the filter parameter as a set descriptor that the server expands, and postIds as an alternative to be used only when IDs are already held. This adds essential semantic meaning to the bare schema types.

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 states the exact action: 'Soft-delete up to 50 scheduler-side posts in ONE call.' It clearly distinguishes from the sibling delete_scheduled_post by explicit contrast and calls out the plural nature of the operation. The verb and resource are specific and unambiguous.

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 an explicit invocation protocol: use filter on the first call to let the server expand the set, pass postIds only when already known, never fan out delete_scheduled_post, and never list first. It also gives a concrete use case ('remove all expired draft posts'), leaving no doubt about when to use this tool.

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