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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering the basic safety profile. The description adds that the tool forwards bug reports and that the conversation parameter aids reproduction. However, it does not clarify what side effects occur (e.g., creating a ticket) or whether authentication is required, leaving some behavioral ambiguity.

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, front-loaded with the primary purpose. The second sentence gives a specific, actionable instruction about the conversation parameter. There is no unnecessary detail, making it highly concise and well-structured.

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 relatively simple, and the description covers the core action and one key parameter. However, it omits information about expected return values, prerequisites like authentication (given the sibling authenticate tool), and the purpose of the context parameter. These gaps are notable given there is no output schema to compensate.

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 carry parameter meaning. It explains that 'conversation' should contain recent messages for reproduction, but does not explain 'message' (the required parameter) or 'context'. The description also calls 'conversation' an array while the schema types it as string, which could cause confusion. Overall, only one of three parameters receives meaningful elaboration.

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 uses a specific verb ('Report') and identifies the resources ('bug, missing feature, or send feedback'). This clearly distinguishes it from sibling tools like show_version and marketplace, leaving no ambiguity about its 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 explicitly states the use case: to report a bug, missing feature, or provide feedback. It also gives a directive to include the conversation array for reproduction. No alternative tools are mentioned, but none are needed since no other sibling handles issue submission, so the context is clear.

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