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

Annotations indicate idempotentHint=true and destructiveHint=false, but no readOnlyHint. The description doesn't contradict annotations. It adds some behavioral context (reproduction data) but doesn't explain what happens after reporting (e.g., whether it's stored, whether it sends a confirmation). With no readOnlyHint, the tool could mutate server-side state, but the description doesn't explicitly state it creates a record or sends a message.

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 description is short and to the point, front-loaded with the purpose and an instruction to include reproduction data. It avoids unnecessary words, though it could be slightly more structured.

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?

With no output schema, no enums, and zero schema coverage, the description must explain the full behavior. It's lacking details on how to structure the conversation array, what format the message should take, any limits, and what happens after submission. The tool is a report action, so it might benefit from explaining whether it's a fire-and-forget or returns a reference.

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 compensate. However, the description only mentions 'conversation array' but doesn't explain the 'message' or 'context' parameters. The 'message' parameter is required and is the core content, but it's not described. The 'context' default is empty and unclear. This leaves much of the meaning undefined.

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 clearly states the tool reports bugs, missing features, or feedback, and mentions including the conversation array for reproduction. This is a specific verb-action combination that distinguishes it from siblings like marketplace or show_version, though it could be more distinct from generic feedback tools.

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 says to include the conversation for reproduction, but doesn't explicitly say when to use this vs alternatives (e.g., when not to use it, or if there are other feedback channels). This is implied but not explicit.

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