Turn comments on or off

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

Goes well beyond the annotations: readOnlyHint=false and destructiveHint=false are already declared, but the description explains WHY it is non-destructive (existing comments are preserved, only new additions are blocked), states the permission requirement, and notes reversibility ('undone with one call'), reinforcing idempotentHint=true with a concrete recovery path.

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?

Front-loaded with the action, then the semantics, permission and reversibility. The opening sentence and the following sentence restate the same purpose, which is mild redundancy, but each remaining clause carries distinct information.

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 boolean toggle with no output schema, the description covers purpose, state effects, authorization, idempotency and reversibility — everything an agent needs to invoke it correctly. The 'as the post menu's Turn off comments does' anchor removes the remaining ambiguity.

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 all three parameters (group, post_id, enabled) are already documented, including 'false turns comments off, true back on'. The description restates the enabled semantics but adds nothing about group or post_id, so the baseline 3 applies.

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 and resource ('turn comments on a post off, or back on') and immediately defines what 'off' means: existing comments stay, nobody can add new ones. That definition implicitly separates it from comment_on_post, delete_post and pin_comment, which an agent can tell apart without opening schemas.

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?

Gives a concrete precondition ('Group admins and moderators only') and the exact state semantics for enabled true/false, plus a confirmation policy ('runs without asking first'). It stops short of explicitly naming when to prefer this over sibling tools such as update_post, but the context is clear.

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