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

Beyond annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false — a non-destructive local write), it discloses that reporting is bounded, deduplicated, and published between reply turns. That is real behavioral context an agent could not infer, though it doesn't say what happens when a duplicate is submitted or whether the report is later visible/reviewable.

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 front-loaded, then constraints, then exclusions. No filler and no restatement of the tool name.

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 simple two-parameter write with no output schema, the description covers purpose, exclusions, and dedup/publication behavior, but leaves the content requirements for explanation and the outcome of a successful or rejected report unexplained. Adequate rather than complete.

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 0%, so the description must carry parameter meaning, and it only half does: "citing its source message" implies message_id identifies the message the problem concerns, but never states the UUID/format expectation or that the message must be in scope. The explanation parameter — the bulk of the actual report content, with 20–1500 char bounds — is not addressed at all.

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 (report) and a specific resource class (a concrete problem, contradiction, error or fix) and requires a source message, which clearly separates it from the generic messaging siblings like post_message. It does not name the sibling it replaces, so it stops short of full differentiation.

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 an explicit exclusion ("No general commentary or response to another problem report"), which effectively routes general commentary to post_message without naming it. It also supplies a positive condition (must cite its source message), but doesn't explicitly say which sibling to use for non-problem messages.

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