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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses real consequences: a removal closes the subreddit to drafts until reopen, a ban closes it for good and skips waiting drafts, and a ban cannot be reopened. This is strong behavioral context a caller could not infer from annotations alone. It does not contradict the annotations.

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 core purpose is front-loaded, and each sentence carries useful information about effects, empty lists, and reopen. But it is a single dense paragraph with run-on phrasing and internal jargon ('grow's confirm.reddit') that reduces readability without adding much 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?

For a write tool with no output schema, the description covers purpose, downstream effects, the reopen parameter, and the empty-list convention, which is enough for correct invocation. Minor gaps remain on error behavior and the notices field details, but the nested schema carries those.

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?

The description explains the 'reopen' parameter (subreddits the founder asked to retry, bans excluded) and the concept of the notices list including its kinds, adding meaning beyond the top-level schema, which has 0% description coverage. However, the notices array fields (id, url, reason, at, subreddit) are only documented in the nested schema, so the description compensates partially rather than fully.

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 names a specific verb (Record) and resource (emails from Reddit's noreply@redditmail.com) and enumerates the notice types (post/comment removal, ban, ban lifted). The purpose is clear, though the internal jargon 'grow's confirm.reddit' forces a re-read and slightly muddies an otherwise precise statement.

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?

It gives usage context for the empty-list case ('Pass an empty list when there are none, so the read counts') and defines reopen, but never states explicitly when to use this tool versus other paths or any exclusions. Guidance is implied through the confirm.reddit flow rather than spelled out.

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