comments_hide

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

The description adds value beyond annotations by noting the operation is asynchronous and listing supported platforms. Annotations already indicate destructive and idempotent behavior; the description reinforces these traits without contradiction.

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 extremely concise—only two short sentences—covering the key points without any extraneous information. It is front-loaded with the action and platforms.

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 description is adequate for a simple tool with three required parameters and full schema coverage. However, it lacks details about success/failure responses, reversibility (though implied by 'comments_unhide'), and implications of asynchronous execution.

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%, so the baseline is 3. The description does not add additional context beyond the schema's parameter descriptions (e.g., 'Post ID', 'Comment ID (Postproxy ID or external ID)'), so no extra credit.

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 action ('Hide a comment') and specifies the platforms (Instagram, Facebook, and Threads). It distinguishes from sibling tools like 'comments_delete' and 'comments_unhide' by using the verb 'hide'.

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?

No guidance is provided on when to use this tool versus alternatives like 'comments_delete' or 'comments_unhide'. The description mentions 'asynchronously' but does not elaborate on expected behavior or when hiding is preferred over deleting.

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