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

Annotations already declare idempotentHint=true, readOnlyHint=false, and destructiveHint=false, covering basic safety traits. The description does not add extra behavioral context such as what happens after submission (e.g., logging, notification) or any side effects. It adds a hint about including conversation data, but that is more about parameters than tool behavior. The description is not contradictory to any annotation, so a score of 3 is appropriate given the bar is lowered by annotations.

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 a single sentence that front-loads the purpose and includes a practical usage hint. Every word earns its place with no fluff, 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?

Given the tool's simplicity (3 parameters, no output schema, no nested objects), the description covers the core use case. However, it lacks details on the 'context' parameter and does not explain expected message format or any post-submission behavior. While annotations provide safety info, the description is minimal and leaves some ambiguity, resulting in a moderate completeness score.

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 for explaining all parameters. It only explicitly mentions the 'conversation' array ('Include the conversation array') and implies 'message' as the main content, but completely omits the 'context' parameter. The schema provides defaults for context and conversation, but the description does not elaborate on their purpose. With 0% coverage, this is a significant gap, hence a score of 2.

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.' This is a specific verb+resource with clear scope. It is obviously distinct from siblings like authenticate, marketplace, or show_version, so it ticks the differentiation box.

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 gives clear context for when to use the tool (bug reporting, feature requests, feedback) and even provides a usage hint about including the conversation array. It does not explicitly mention exclusions or alternatives, but the sibling list makes it obvious that other tools serve different purposes. This is adequate guidance.

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