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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the write-but-harmless profile is already visible. The description adds real, non-redundant behavior: 'Reports are read, not published' tells the agent submissions aren't public, and the 300-char cap signals truncation behavior. It stops short of saying whether a confirmation or reply is returned.

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?

Three short sentences: purpose first, calling constraint second, privacy note last. Every sentence carries distinct information and nothing is repeated from the title or schema.

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 3-parameter, no-output-schema tool, the description plus full schema coverage covers kinds, target page, message limit, and visibility. The only gap is what happens after submission (confirmation, response, rate limits), which is minor given the low-stakes, non-destructive nature.

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 the baseline is 3 and the schema already carries the enum meanings and field purposes. The description still contributes beyond schema: 'one issue per call' is a calling convention the schema does not encode, and restating the 300-character limit reinforces the constraint on message.

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+recipient+content ('Tell the maintainers of miow what you needed and did not find, what is wrong, or what broke'), which no sibling covers — the siblings are all site/wiki CRUD tools. An agent can distinguish this from every other tool in the list 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?

The description enumerates the triggering situations (missing content, wrong content, breakage) and adds a calling constraint, 'One issue per call,' which shapes how the agent batches. It does not name when not to use it or an alternative channel, but no sibling competes for this purpose.

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