Bulk post actions

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

Annotations already declare destructiveHint=true and readOnlyHint=false, covering the mutation risk. The description adds that operations affect multiple posts at once, but doesn't disclose consequences like irreversibility of deletes or partial-failure behavior. It stays consistent with annotations without adding much beyond them.

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?

Two tight sentences: the first states the purpose and actions, the second states usage. No wasted words and the key information is front-loaded.

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 bulk destructive operation, the description covers purpose, when to use, and the action set, and the schema documents all parameters. It would benefit from a note about return format or partial-failure handling, but the essentials for invoking the tool correctly are present.

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 100%: action's enum, postIds, and scheduledAt each have descriptions in the schema. The tool description adds no extra parameter semantics, so it meets the baseline for fully documented schemas.

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 resource ('multiple posts') and the specific verb ('Perform a bulk action'), then enumerates the supported actions (delete, retry, reschedule). It distinguishes itself from sibling single-post tools by emphasizing 'many posts in a single request'.

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 second sentence gives an explicit when-to-use trigger: 'Use this when the user wants to delete, retry, or reschedule many posts in a single request.' However, it doesn't explicitly mention single-post alternatives or exclusions, so it's clear but not fully complete.

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