instagram_delete_post

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

The description discloses permanent deletion, but does not mention auth requirements, side effects, or any other behavioral traits. No annotations are provided, so the description carries the burden but is minimal.

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—two sentences with no fluff. Every word contributes to the core message.

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?

Despite a simple tool with one parameter and an output schema (not shown), the description lacks parameter explanation. It achieves minimal completeness but leaves a gap for the agent to infer parameter semantics.

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 description does not explain the sole parameter 'media_id_or_url'. With 0% schema description coverage, the description should clarify what the parameter represents (e.g., ID or URL of the post). The parameter name alone is insufficient.

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 'Permanently delete a post' using a specific verb and resource, and distinguishes it from sibling tools like instagram_archive_post by emphasizing permanence.

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 phrase 'cannot be undone' implies caution, but there is no explicit guidance on when to use this tool versus archiving or other alternatives. Usage context is only implied.

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