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

Annotations already declare idempotentHint=true and destructiveHint=false, covering the safety profile. The description adds the actionable detail of including the conversation array for reproduction. However, it does not disclose post-invocation behavior such as whether the report is sent externally or what the response contains.

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 extremely concise, comprising two short sentences that front-load the core purpose and then add a single crucial usage hint. Every word earns its place, and there is no redundancy or 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?

This is a simple tool, and the description covers its primary purpose and provides one key parameter hint. However, the absence of an output schema and lack of clarity about the conversation parameter leave some gaps. The annotations cover mutation behavior, but the description could be more complete about expected outcomes or error handling.

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 does add meaning to the 'conversation' parameter by mentioning it as an array, but this contradicts the schema type (string) and could mislead an agent. The 'message' and 'context' parameters are left unexplained, providing insufficient guidance.

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 what the tool does with a specific verb and resource: 'Report a bug, missing feature, or send feedback.' It also includes a specific instruction about including the conversation array, which further clarifies its purpose. This distinguishes it from sibling tools like show_version or authenticate.

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 makes it clear the tool is for reporting issues or feedback, which is sufficient context for when to use it. It does not explicitly mention alternatives or exclusions, but no other sibling tool overlaps in functionality. Thus, it provides clear usage context without formal guidance.

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