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

Annotations provide idempotentHint=true, readOnlyHint=false, and destructiveHint=false, indicating a non-readonly but non-destructive operation. The description adds that the conversation array is needed 'for reproduction,' implying the data is used for debugging. However, it does not disclose potential side effects (e.g., sending data to a server, possible delays, or that the report is stored). With annotations available, the description adds some context but not rich behavioral detail.

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 two sentences with no filler. It front-loads the core action and then adds a concise, actionable instruction. Every word earns its place, making it highly efficient and easy to scan.

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?

Given the tool has 3 parameters (one required) with no schema descriptions, no output schema, and only sparse annotations, the description is insufficient. It covers the overall purpose and one param (conversation) but fails to explain the required 'message' and optional 'context' parameters. It also does not mention what happens after a successful report (e.g., confirmation, no response). For a reporting tool with this complexity, the description is under-specified.

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. It explicitly mentions the 'conversation' parameter ('Include the conversation array'), providing meaning for that param. However, it does not explain the required 'message' parameter (presumably the bug description) or the 'context' parameter (which has a default). The purpose implies message content, but without explicit mapping, the description only partially clarifies parameter meanings.

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.' It uses a specific verb ('Report') and identifies the resource (bug, missing feature, feedback). While it does not explicitly differentiate from siblings, the sibling tools are unrelated (e.g., authenticate, marketplace), so no confusion arises. The added instruction about including the conversation array reinforces the purpose.

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 by stating what the tool does, but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. The instruction to 'Include the conversation array with recent messages for reproduction' gives context for proper invocation, but there is no exclusion or comparison to other tools. Since siblings are unrelated, this is minimally adequate but lacks explicit guidance.

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