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

Goes well beyond the annotations: annotations only say readOnlyHint=false and openWorldHint=true, while the description discloses the moderation lifecycle ('stored as pending'), that nothing publishes automatically, that email is stored but never published, that name/affiliation/position/body do get published, and that it acts on the user's behalf. That is exactly the context an agent needs before a public write.

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 and the two hard requirements, then the moderation and consent details. Slightly repetitive ('nothing is published automatically' largely re-says 'stored as pending — AIO reviews every comment before publishing'), but no sentence is filler.

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?

No output schema exists, and the description compensates by explaining the resulting state (pending, moderated, never auto-published) and the failure mode (closed window). For a non-idempotent public write, nothing an agent needs in order to call it responsibly is missing.

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%, so every parameter is already documented, and much of the description's field talk (email stored never published, name as published) restates schema text. It does add one genuine signal — that name, affiliation, position, and body all become part of the published record — but that is marginal over the schema, so baseline 3 fits.

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 ('Submit a comment on an open AIO public RFC') and immediately narrows scope to open RFCs, which separates it from get_rfc and list_rfcs in the sibling set. An agent can tell what this does without opening the schema.

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?

Explicitly gives preconditions ('Requires a real name and a working email address'), the blocking condition ('a comment on an RFC whose window has closed is rejected'), and a consent rule ('ask the user before calling it, and use their own words'). It even warns that every RFC published so far is closed, which is the decisive usage fact.

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