Set Comment Hidden

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

Annotations already declare idempotent, destructive, and open-world behavior, so the bar is lower; the description adds genuinely non-structured information — that hidden comments remain visible to their author rather than disappearing. It does not contradict the destructive hint, though it omits any permission requirements.

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?

Two short sentences, zero filler, with the action and its state consequence front-loaded.

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 mutation tool with annotations and an output schema, the description covers the core effect well. It leaves out authorization requirements and any side effects on existing replies/notifications, which would matter for a destructive-flagged write.

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 67%, with the key 'hidden' boolean undocumented in the schema; the description's 'Hide (or unhide)' clarifies that it is a toggle in both directions, but says nothing about the page-scoping parameter or comment id format, which the schema already handles.

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?

States a specific verb pair (hide/unhide) and resource (comment) with the resulting state semantics — visible only to the author. This clearly differentiates it from sibling tools like delete_comment, list_comments, and add_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 implies the use case (make a comment visible only to its author, or reverse that), but never states when to choose this over delete_comment or add_comment, and gives no prerequisites such as needing to be the author or a page admin.

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