threads_delete_post

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

No annotations are provided, so the description carries the full burden. It discloses irreversibility and a specific rate limit, which are critical behavioral traits for a delete operation. However, it could also mention what happens on success or error (e.g., if post ID is invalid).

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, no wasted words. The action is stated first, followed by critical warnings. Perfectly front-loaded and 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 delete tool with one parameter and no output schema, the description covers the key behavioral aspects (irreversibility and rate limit). It is mostly complete, though it could briefly note error handling or expected return value (e.g., empty response).

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 already fully describes the 'post_id' parameter with 100% coverage. The tool description adds no additional meaning beyond what the schema provides, so it meets the baseline for schema coverage but does not go further.

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 a Threads post' with a specific verb and resource. It is distinct from sibling tools, which are for Instagram or other Threads actions like getting posts or publishing.

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 mentions the action is irreversible and rate limited (100 per 24 hours), providing helpful constraints. No explicit alternatives are needed since this is the only tool for deleting Threads posts, but a note on when not to use it (e.g., if deletion is not desired) is missing.

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