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

The annotations indicate idempotentHint=true and readOnlyHint=false, but the description does not explain the side effects (e.g., creating a ticket, sending a message). It doesn't state what happens after reporting or if any permissions are needed.

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?

Two short sentences convey the essential information without fluff. It is front-loaded with the primary action and clearly states what to include.

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?

For a simple feedback tool, it explains the main param (conversation) and purpose. However, it doesn't mention what happens after reporting, nor does it clarify the 'context' parameter, leaving some gaps.

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 description mentions 'conversation array' explicitly, giving context for that parameter that the schema lacks. However, 'context' is not explained, and 'message' is only implied. With 0% schema description coverage, more detail would be helpful.

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 purpose: 'Report a bug, missing feature, or send feedback.' This is unambiguous and directly tells the user what the tool does. The title 'Report Bug' reinforces this.

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?

It says to include the conversation array for reproduction, but does not specify when to use this tool versus other siblings like 'marketplace' or 'show_version'. Also lacks prerequisites or conditions for use.

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