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

The annotations indicate idempotentHint=true and destructiveHint=false, so the description does not contradict them. The description adds context that the tool is for reporting and that it expects a conversation array for reproduction. It doesn't detail side effects, but idempotency and non-destructive nature are already covered by annotations, which lowers the bar. The description adds the reproduction guidance, which is useful.

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 concise, two sentences, and front-loaded with the main purpose. Every word earns its place, providing the essential actionable instruction without unnecessary fluff.

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 straightforward (reporting feedback) with three parameters and no output schema. The description is sufficient for the agent to understand what to do, especially with the reproduction hint. It lacks details on response format or side effects, but given the low complexity and annotation coverage, it is fairly 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?

The schema description coverage is 0%, so the description must compensate. The description explains the 'conversation' parameter partially by saying to include it, but it does not elaborate on 'context' or 'message' beyond the schema's basic definitions. The description adds a bit of meaning by specifying that conversation should contain recent messages, but it lacks detail on the other parameters. Baseline is 3 due to low coverage, but it does not fully compensate.

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/feature/feedback). It distinguishes itself from siblings like 'authenticate' or 'connect' by focusing on bug reporting and feedback.

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 explicit guidance on what to include: 'Include the conversation array with recent messages for reproduction.' This tells the agent when and how to use the tool (when reporting an issue) and what supplementary information is needed. However, it does not explicitly state when not to use it or mention alternatives, but the context is clear enough.

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