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

Annotations already provide readOnlyHint=false and destructiveHint=false, so the description's added value is the instruction to include the conversation array for reproduction. This gives useful context about what to provide, but it does not disclose potential side effects (e.g., data being sent, confirmation behavior) beyond the annotations.

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 a single, concise sentence that front-loads the purpose and immediately provides the key instruction about the conversation array. No unnecessary words.

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 with no output schema, but the description still omits the 'context' parameter and does not mention what happens after reporting (e.g., confirmation, ticket creation). It is adequate but not fully complete for an agent to understand all aspects of the operation.

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 schema description coverage at 0%, the description partially compensates by explaining 'conversation' (for reproduction) and implying 'message' (the content to report). However, the 'context' parameter remains unexplained, leaving a gap in full parameter understanding.

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 with a specific verb ('Report') and resource ('a bug, missing feature, or send feedback'). It distinguishes itself from sibling tools like show_version or authenticate, which serve entirely different 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 implies usage (when you have a bug/feature/feedback) but does not explicitly mention when not to use it or provide alternatives. There is no exclusionary guidance, only the inferred purpose.

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