delete_post

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

No annotations exist, so description must disclose behavior fully. It states 'Delete' (mutation) and limits to 'scheduled or draft post', which is a key constraint. However, it omits side effects, reversibility, permissions, or output details. Important information missing beyond the basic 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?

Two sentences, front-loaded with the key action and resource. The arg description is directly relevant. No wasted words; highly efficient.

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 simple 1-parameter tool with an output schema, the description covers the basics. However, it misses critical context: whether the post must belong to the user, if deletion is permanent, or if the restriction to scheduled/draft is enforced. Not fully complete for safe agent usage.

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?

With 0% schema description coverage for post_id, the description adds meaning by stating 'The ID of the post to delete'. This clarifies what the parameter represents. However, it does not add format or validation hints beyond the schema's type string.

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 'a scheduled or draft post from Hootsuite'. It distinguishes from sibling tools (create_post, get_*) but could be more precise about why only scheduled/draft posts are mentioned.

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 usage is implied (delete a post) but there is no explicit guidance on when to use or not use this tool, nor alternatives. Since siblings don't include another delete tool, it's acceptable but still lacks explicit when-not guidance.

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