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

Substantially exceeds the annotations: no sign-in required, rate limit of 'a few messages per day', 1000-character cap, human review over following days with no automatic reply, and a precise privacy statement (GitHub id retained only if signed in, nothing else). The 'do not wait for one' note is exactly the kind of expectation-setting an agent needs before calling a fire-and-forget 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?

Purpose is front-loaded in the first clause, with limits, latency, privacy, and routing following in a sensible order. The em-dash list is denser than necessary and could be trimmed, but every sentence supplies information an agent would otherwise have to guess.

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?

Output schema exists, so return values need not be explained; the description instead covers the things structured fields cannot: anonymous access, throttling, human-only handling, expected delay, and data retention. Nothing material is missing for correct invocation.

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 `tool`, `message`, and `error_code` fields are already fully documented with examples. The description echoes the 1000-character limit and reinforces privacy ('nothing else about you is'), but adds no syntax or selection guidance for the parameters beyond what the schema carries; 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?

Opens with a specific verb and audience: telling the people running the service that something went wrong or is unclear, then enumerates the concrete cases (unexplained error, wrong result, misleading docs, missing tool). No sibling tool does anything similar, so an agent can route here without opening a 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?

Gives clear trigger conditions — unexplainable errors, suspicious results, misleading docs, absent tools — and notes that 'every refusal from this service points here', which is an explicit inbound routing rule. It stops short of naming exclusions or alternative siblings (e.g., use node_status for status checks instead), so it is clear context rather than a full when/when-not decision table.

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