social_media_posting_delete_csv_post

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description does not need to repeat those. However, the description adds no additional behavioral context beyond the annotations—such as effects on related data, irreversibility, or any cascading actions. Given that annotations cover the core safety profile, the description is adequate but not enriching.

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 extremely concise—three words—which is efficient and avoids verbosity. However, it is so minimal that it borders on tautology, essentially restating the tool name. It lacks any structuring or additional context that would aid an agent, but it does not waste words.

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 simplicity (3 params, 2 required, no output schema) and the annotations covering destructive/idempotent behavior, the description is minimally sufficient. However, ambiguity with sibling deletion tools (e.g., delete_post vs. delete_csv vs. this tool) is not resolved, and no guidance on what constitutes a CSV post is provided. An agent might call the wrong deletion tool without clearer context.

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 input schema provides descriptions for all three parameters (csvId, postId, locationId), including a default for locationId. Since schema description coverage is 100%, the schema fully documents the parameters. The description contributes nothing beyond that, so it meets the baseline but adds no extra meaning.

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 a specific resource (CSV Post), which provides clear intent. However, it does not differentiate this from sibling tools like social_media_posting_delete_post (which likely deletes a regular post) or social_media_posting_delete_csv (which deletes a CSV file). The name and description are nearly identical, so an agent might confuse which resource is being deleted without additional context.

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 usage guidance is provided. The description does not indicate when to use this tool versus other deletion tools (e.g., delete_post, delete_csv, bulk_delete_social_planner_posts). There is no mention of prerequisites, when CSV posts are applicable, or any conditions that select this tool.

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