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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description does not contradict these annotations. It adds minimal behavioral context: it implies a reporting action and suggests including conversation for reproduction, but does not disclose side effects, such as whether the report is stored or sent externally. Since annotations cover the safety profile, a score of 3 is appropriate.

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: one sentence, no wasted words. It front-loads the purpose and provides a key usage instruction. It earns a perfect score for conciseness and structure.

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 that there is no output schema and the description is the only source of context beyond annotations, it falls short for a tool with 3 parameters. It does not explain the return value, does not specify the format of 'conversation', and does not clarify the meaning of 'context'. The description provides a basic purpose but leaves significant gaps for an agent to use it correctly.

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% – the description does not explain the 'message', 'conversation', or 'context' parameters. The required 'message' parameter is not described at all, and the 'conversation' parameter's format is only hinted via the description's instruction to 'include the conversation array'. With no parameter details in the description and no coverage in the schema, the description fails to compensate for the complete lack of parameter semantics.

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 specific verbs ('report', 'send') and identifies the resources (bug, feature, feedback). However, it doesn't explicitly differentiate from siblings, though sibling tools like 'marketplace' or 'show_version' are clearly different. The title 'Report Bug' aligns with the description.

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 implies usage context: it is for reporting issues and includes instructions to 'Include the conversation array with recent messages for reproduction.' However, it does not explicitly state when not to use this tool or mention alternatives among siblings. The guidance is clear but not comprehensive.

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