delete_social_media_post

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

With no annotations provided, the description carries the full burden of disclosure. It states the tool deletes a post, which is clear, but does not specify whether deletion is permanent, reversible, or if it requires specific permissions. The description is minimally transparent for a destructive action.

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 sentence with no wasted words. It is appropriately sized for the tool's simplicity, though it could benefit from a brief additional context without becoming verbose.

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 (2 parameters, no output schema, no nested objects), the description is minimally adequate. However, it lacks details about the relationship between the two parameters, whether both are required, or what happens if the post does not exist. For a delete operation, more completeness would be beneficial.

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% with both 'group_id' and 'post_schedule_id' already described. The description adds no additional meaning or context for the parameters beyond what the schema provides. According to the rules, baseline 3 is appropriate when schema coverage is high.

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 action (delete) and the resource (published social media post). It is specific and uses a verb+resource structure. However, it does not differentiate from sibling tools like 'delete_social_media_draft' which also deletes content, so it misses the opportunity to clarify the distinction between deleting drafts versus published posts.

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. For example, it doesn't explain when to delete a published post versus updating it or deleting a draft. There is no mention of prerequisites or contexts where deletion is appropriate, leaving the agent without decision-making cues.

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