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

The annotations already declare destructiveHint=false and idempotentHint=true, so the safety profile is clear. The description adds that the tool is for reporting and that conversation data should be included, but it does not disclose what happens after submission (e.g., whether a response is returned, rate limits, or data handling). This is adequate given 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 two sentences long with no filler. It front-loads the purpose and then provides usage guidance. Every sentence adds value.

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 3 parameters and no output schema, the description covers the core purpose and one parameter. However, it lacks details on the return value, potential limitations (e.g., message length), and what happens after reporting. It is minimally complete but not rich.

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 explains the 'message' and 'conversation' parameters (message is the required content, conversation should include recent messages for reproduction). However, it does not explain the 'context' parameter. With 2 out of 3 parameters partially explained, it provides some meaning but misses the third parameter.

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 identifies a specific verb (report) and resources (bug, feature, feedback), and it distinguishes itself from sibling tools by being the only feedback submission tool.

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 to 'Include the conversation array with recent messages for reproduction.' This tells the agent when to use this tool (to report issues) and what data to include. There are no similar siblings, so alternatives are not needed.

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