social_media_posting_bulk_delete_social_planner_posts

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

The description says 'Delete', which implies a destructive operation, but the annotations set destructiveHint=false, indicating the tool is not destructive. This is a direct contradiction. The description also fails to disclose any side effects, reversibility, or permission requirements.

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 concise phrase with no wasted words. It is efficiently front-loaded and to the point, though it sacrifices completeness for brevity.

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 delete operation with no output schema and minimal annotation, the description is inadequate. It does not mention what happens to the posts, whether deletion is permanent, what the response contains, or any prerequisites. The contradictory annotation further reduces completeness.

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 coverage is 100% with both parameters documented, but the descriptions are vague ('Requested Results' for postIds). The tool description adds no additional parameter meaning, relying entirely on the schema. Baseline 3 is appropriate given high coverage, though the schema descriptions themselves are weak.

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 a specific verb ('Delete') and resource ('Social Planner Posts') and implies bulk operation via the name and description. It clearly identifies the action but does not explicitly differentiate from siblings like social_media_posting_delete_post, though the 'Bulk' prefix provides some distinction.

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 is provided on when to use this tool versus alternatives (e.g., singular delete_post, delete_csv_post). The description offers no context about selection criteria or prerequisites, leaving the agent to infer usage from the name alone.

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