Hide or unhide a reply

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

Beyond the annotations (mutation, idempotent, non-destructive), the description discloses two non-obvious behaviors: hiding a top-level reply cascades to nested replies, and the operation is reversible in one call so no confirmation is needed. This is valuable context that helps an agent predict side effects.

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 twwo concise sentences: the first states the action, the second gives the two critical behavioral caveats. There is no wasted wording or repetition of schema content.

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 three-parameter mutation with rsich annotations, the description covers action, scope, cascade behavior, and reversibility. There is no output schema, but the tool is simple enough that the description is complete without detailing return values.

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 adds general behavioral context around hide and reply_id (cascade, reversibility), but no parameter-specific detail beyond what the schema already 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 states a specific verb ('Hide'/'unhide'), a clear resource ('a reply on one of your posts'), and a distinguishing condition ('Hiding a top-level reply cascades to everything nested under it'). No sibling tool covers this exact action, so the purpose is unambiguous.

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 gives clear context: this tool is for hiding/unhiding replies on your own posts, with the cascade behavior and reversible one-call nature. It does not name alternatives or exclusions, but no sibling tool is an obvious substitute, so the intended usage is well implied.

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