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

The description adds a genuinely new behavioral fact not present in the annotations: 'One-way: no reply is sent.' That tells the agent not to expect a response loop, which annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false, idempotentHint=false) do not convey. Rate limiting or throttling behavior is not mentioned, keeping it short of a 5.

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?

Two short sentences, zero filler, with the core action and the qualifying content stated first and the one-way caveat second. Every clause earns its place.

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?

All four parameters are documented in the schema, an output schema exists, and annotations cover the safety profile, so the description only needs to add the directionality and intent — which it does. Only a note on whether submissions are anonymous or how they are acknowledged would push this higher.

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%, including a fully spelled-out enum for 'category', so the schema already carries the semantic load. The description's examples ('a wrong text, a missing amendment, a broken answer') loosely reinforce the category values but add no format, length, or placement guidance beyond the schema's 'Max 1,000 characters'. 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?

The description names a specific action (tell the maintainer) and enumerates the exact content classes that qualify — wrong text, missing amendment, broken answer, or praise. This is clearly distinguishable from every sibling, which are all read-only regulatory lookup tools (get_article, search_text, etc.).

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 concretely lists triggering situations (a wrong text, a missing amendment, a broken answer, or that the server helped), which is strong when-to-use guidance. It does not state when-not to use it, but no competing alternative exists among the siblings, so the gap is minor.

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