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

Annotations already disclose readonlyHint=false and destructiveHint=false, and idempotentHint=true. The description adds no further behavioral context such as whether the feedback is sent to a ticketing system, if it requires authentication, or what happens after submission. Given annotations cover safety traits, the description does not contradict them but also does not enrich the agent's understanding of side effects beyond the purpose.

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 core purpose, and every word adds value. No fluff or redundancy. The instruction about conversation is placed immediately after the purpose, making it clear and actionable.

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 with 3 parameters and no output schema. The description covers the primary action and gives a key usage hint. It misses explaining the 'context' parameter, but given the simplicity and the presence of annotations, the description is mostly sufficient for an agent to invoke the tool correctly. Minor gaps do not significantly impede usage.

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 explicitly explains the 'conversation' parameter: 'Include the conversation array with recent messages for reproduction,' which adds meaning beyond the schema's bare string type. However, it does not clarify the 'context' parameter, and 'message' is obvious from the purpose. Partial compensation, not fully comprehensive.

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 and resources, and is distinct from sibling tools like authenticate, marketplace, or show_version. The purpose is unambiguous and easily understood.

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 clear context for when to use the tool (reporting bugs, missing features, or feedback) and includes a key usage instruction: 'Include the conversation array with recent messages for reproduction.' It does not explicitly mention alternatives or when not to use it, but given the sibling set, this tool is uniquely for reporting. This is close to ideal but lacks explicit exclusions.

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