ig_delete_comment

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

With no annotations provided, the description carries the behavioral disclosure burden. It does disclose the key trait that the action is irreversible ('Action irréversible'), which is important for a destructive operation. It does not mention permissions, rate limits, or cascading effects, so coverage is partial.

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 two short sentences with no extraneous content. It front-loads the core action and then adds the critical irreversibility warning. Every word earns its place.

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 one-parameter delete operation with an output schema present, the description provides the essential action and a caution about irreversibility. It does not mention permissions or which specific comment types are eligible, but the core context is adequate. Missing usage and parameter guidance lower the completeness score.

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 0% and the description does not mention comment_id at all, so it adds no parameter-level meaning beyond the schema. The parameter name is self-explanatory, but the description fails to compensate for the low schema coverage, e.g., by noting that comment_id is the ID of the comment to be deleted.

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 uses a specific verb and resource: 'Supprime un commentaire Instagram' (deletes an Instagram comment). It clearly distinguishes this from sibling tools like list_ig_comments or ig_reply_to_comment, and from delete_page_post, by specifying the resource as an Instagram comment.

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 implies when to use the tool: whenever an Instagram comment needs to be deleted. However, it does not explicitly state exclusions, prerequisites, or alternatives, leaving the agent to infer usage from the verb-resource pair.

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