Turn comments on or off for an Instagram post

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

Annotations already mark this as non-read-only, open-world, and potentially destructive. The description adds useful behavioral context: existing comments are preserved either way, the post must belong to the profile, and the operation is Instagram-only.

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 front-loaded, compact, and waste-free. It states the action, the re-enable behavior, the preservation of existing comments, and the platform restriction in three short sentences.

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?

The tool has an output schema and full parameter documentation, so return values need not be explained in the description. The description covers platform scope, ownership, and side effects well; only edge cases such as permission failures are left implicit.

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 100%, with all three parameters documented in the schema. The description reinforces the meaning of `enabled`, but does not add substantial semantics beyond what the schema already provides.

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 states a specific verb and resource: turning commenting off or back on for an Instagram post. It also scopes the action to the profile's own posts and limits it to Instagram, which separates it from comment-level siblings like hide_comment or delete_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?

It clearly covers the two usage modes: off by default and back on with `enabled: true`. It also gives an important exclusion, "Instagram only," and restricts the action to the profile's own posts, though it does not explicitly compare against alternative comment-management tools.

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