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

Annotations indicate idempotentHint=true, readOnlyHint=false, and destructiveHint=false, which already signal the tool's safety profile. The description adds context by requiring the conversation for reproduction, but does not disclose what happens after submission (e.g., where the report goes, confirmation behavior). With annotations present, this is acceptable but not rich.

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 concise sentences, front-loaded with the action and ending with a actionable instruction. No wasted words, no repetition of schema fields.

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 simple (3 params, no output schema, no nested objects), and the description covers the overall use case and one parameter well. However, the required 'message' parameter is unexplained, and there is no mention of return values or post-submission behavior, so completeness is only adequate.

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 carries the burden of explaining parameters. It clarifies that 'conversation' should contain recent messages for reproduction, but provides no guidance for the required 'message' parameter or the optional 'context.' The primary input is undocumented, leaving a significant gap.

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's purpose: 'Report a bug, missing feature, or send feedback.' This distinguishes it from sibling tools (authenticate, connect, marketplace, show_version, toolkit_info) which serve unrelated functions.

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 provides clear context for when to use the tool (bug reporting, feature requests, feedback) and explicitly instructs to 'Include the conversation array with recent messages for reproduction.' It does not explicitly mention alternatives or exclusions, but siblings are unrelated, so the usage context is sufficient.

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