zernio_hide_comment

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

With no annotations, the description states the core behavior (hide from public, not delete), but lacks details on reversibility, visibility to owner or admins, or required permissions. The sibling tool zernio_unhide_comment implies reversibility, but it's not stated.

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 sentences, no unnecessary words, front-loaded with the action. Every sentence adds value.

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 covers the main purpose and differentiates from deletion. It lacks explanation of reversal or output, but for a simple hide tool with full schema coverage and sibling tools, it is adequate.

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% (both commentId and accountId have descriptions). The description does not add any parameter-level meaning beyond the schema, earning the baseline score.

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 the specific verb 'hide' and the resource 'comment from public view on a post', and clarifies it is not deleted. This distinguishes it from sibling tools like zernio_delete_comment and zernio_unhide_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 when to use: to hide a comment without deleting. It distinguishes from deletion by stating 'not deleted but hidden'. However, it does not explicitly provide when-not-to-use or mention alternative tools.

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