ig_toggle_comments

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

Annotations already indicate readOnlyHint=false (modification) and destructiveHint=false, and idempotentHint=true. The description adds no behavioral context beyond stating the action, such as what happens to existing comments when disabled (e.g., hidden vs deleted), required permissions, or rate limits. The description does not contradict annotations.

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 a single, efficient sentence that immediately conveys the tool's purpose. No unnecessary words or redundant information.

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 toggle tool with two parameters and no output schema, the description is adequate but incomplete. It lacks information about the effect on existing comments (e.g., are they hidden or removed when disabled?) and required account permissions. The completeness is acceptable but has notable gaps.

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 coverage is 100% with descriptions for both parameters (media_id and enabled). The tool description does not add further meaning beyond what the schema provides. Baseline score 3 is appropriate.

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 tool enables or disables comments on an Instagram media post. It uses a specific verb ('toggle') and resource ('comments on a media post'), distinguishing it from sibling tools like ig_hide_comment (which hides a single comment) or ig_delete_comment (which deletes a 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 provides no guidance on when to use this tool versus alternatives such as ig_hide_comment or ig_delete_comment. It does not mention prerequisites, such as needing to be the media owner, nor does it exclude contexts where comments cannot be toggled (e.g., archived posts).

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