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

The annotations already declare destructiveHint=true and readOnly=false, so the description is not required to restate the safety profile. It adds useful context that the operation is scoped to an exact, pre-resolved comment and warns against guessing from unstructured input, but it does not reveal much beyond what the annotations and name imply.

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 opening sentence is clear and the resolver guidance is well labeled, but much of the description duplicates the parameter descriptions in the schema nearly verbatim. This repetition makes the description longer than necessary without adding new 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 destructive 4-parameter tool with full schema coverage, the description provides sufficient resolver chains and anti-misuse guardrails to call it correctly. It is slightly incomplete because one referenced comment resolver is missing from the sibling tool list, but the overall guidance is strong.

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% and the schema already contains the same detailed resolver and 'never pass' guidance for post_id and comment_id. The description therefore adds little new parameter meaning beyond what the input schema 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 names the exact action and target ('Remove the user's reaction from one exact comment'), clearly distinguishing this from related tools like social_remove_post_reaction and social_react_to_comment. It emphasizes the precise scope of the operation without ambiguity.

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 gives concrete resolver chains for obtaining the post_id and comment_id, and explicit 'Never pass' exclusions for text, author IDs, and URLs. It does not explicitly steer the agent toward this tool versus the sibling post-reaction removal tool, and it references instagram_list_post_comments, which is not present in the provided sibling list.

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