instagram_delete_media

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

Beyond the annotations (destructiveHint=true), the description warns that deletion is permanent, cannot be undone, and that 'Instagram keeps no copy you can restore from.' It also discloses the single-tool scope (only the logged-in account's own posts) and the write-permission requirement. This adds significant behavioral context beyond what annotations provide.

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 well-structured: a front-loaded purpose sentence, followed by essential warnings and usage guidance, then a clear Args/Returns section. Every sentence contributes—no filler or redundancy. It is concise yet complete.

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 destructive operation, the description covers all critical aspects: irreversibility, verification step, write-permission requirement, and the return format. Combined with the output schema (not shown here but indicated as present), the agent has everything needed to call the tool correctly and safely.

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 schema already provides full documentation for the media parameter ('Post URL, shortcode or media id of one of YOUR posts') with 100% coverage. The description's Args section restates this almost verbatim, adding only the phrase 'to delete' which is obvious. Per the rubric, high schema coverage sets a baseline of 3, and the description adds no meaningful new parameter semantics.

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 opens with 'Permanently delete one of the logged-in account's own posts,' which is a specific verb (delete) and resource (own posts). It clearly distinguishes this from sibling tools like instagram_get_media, instagram_like_media, or instagram_upload_photo by focusing on permanent deletion of one's own content.

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 explicitly instructs to first confirm the post with the owner and read it back using instagram_get_media before deletion. It also states the prerequisite INSTAGRAM_ALLOW_WRITES=true, which is a clear condition for use. This helps the agent decide when to invoke this tool versus alternative operations.

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