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

Annotations already cover safety-related traits: readOnlyHint is false, destructiveHint is false, and idempotentHint is true. The description adds the reproduction context but does not disclose what happens after a report is submitted, such as whether confirmation is returned or whether any follow-up occurs.

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 one sentence and front-loads the core purpose before giving one essential parameter guideline. No word is wasted and no modifier is repeated.

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?

The tool is fairly simple, and the annotations provide safety and idempotency context. However, the description leaves important input semantics to the caller's inference, especially for the required 'message' parameter and the optional but undocumented 'context' parameter, so it is adequate but not fully 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 the parameter semantics. It explains that 'conversation' should contain recent messages for reproduction, but it does not clarify the meaning of 'message' or 'context', and calling 'conversation' an array could confuse callers since the schema types it as a string.

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 opens with the specific verb 'Report' and names its exact targets: bug, missing feature, or feedback. This makes the tool's purpose immediately clear and distinguishes it from unrelated siblings like authenticate, marketplace, and show_version.

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 directly states when to use the tool: reporting a bug, missing feature, or sending feedback. It also gives a concrete usage hint by asking the caller to include the conversation array for reproduction, though it does not explicitly list any alternatives or 'when not to use' scenarios.

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