comments_unhide

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

Annotations already mark it as non-readOnly, non-destructive, and idempotent. The description adds the 'asynchronously' behavior and platform support (Instagram, Facebook, Threads), providing useful context beyond 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?

A single sentence that is front-loaded with the action and includes only essential information (platforms). No wasted words.

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 unhide operation with 3 required parameters, no output schema, and comprehensive annotations, the description is complete and sufficient. It mentions key platforms and the asynchronous nature.

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% and parameter descriptions are present but minimal. The tool description does not add any extra meaning or format details beyond the schema, so it meets the baseline.

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 (unhide) and the resource (a previously hidden comment), distinguishing it from siblings like comments_hide or comments_delete.

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 the tool should be used after hiding a comment, but does not explicitly state when to use vs alternatives or exclude cases where comment is already unhidden (though idempotentHint covers this).

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