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

Annotations already declare idempotentHint=true and destructiveHint=false, so the tool is implied safe. The description adds value by explaining that including the conversation array helps reproduction, which gives context on side effects (none destructive). It does not exceed the annotation baseline significantly, but provides a small extra behavioral insight.

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 only two sentences, with no filler words. Every word serves a purpose, and the most actionable guidance (including the conversation array) is stated upfront. It is concise without losing necessary detail.

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 low-complexity tool with no nested objects, no output schema, and a single required parameter, the description covers the key aspect (reproduction through conversation). It does not describe return values, but that is not expected given the lack of output schema. Minor gaps like what happens after submitting are absent, but they are not critical for this tool's simplicity.

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?

With 0% schema description coverage, the description must carry parameter documentation. It explicitly mentions the 'conversation array' (mapping to the 'conversation' param) and implies it should contain recent messages, but it does not explain 'context' or 'message'. The description partially covers the parameters but leaves two of the three undocumented, so it underperforms for a zero-coverage schema.

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 uses a clear verb+resource pattern ('Report a bug, missing feature, or send feedback') and distinguishes the tool from siblings like 'connect' or 'marketplace'. It lacks a definitive scope statement, but the purpose is immediately understandable and non-tautological.

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 implies the tool should be used when the user wants to report issues or provide feedback, and instructs to include the conversation array for reproduction. However, it does not explicitly state when not to use it or name alternatives, though the instruction is clear enough for common scenarios.

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