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

Annotations already define the tool as idempotent and non-destructive, so the description doesn't need to repeat these. It adds the useful context that the conversation array is needed for reproduction, which hints at the tool's intended use. However, it doesn't disclose any potential side effects or expected response behavior, so it remains at the basic level.

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 with no unnecessary words. It front-loads the purpose and immediately follows with the key usage instruction. Every sentence adds value, making it an exemplar of concise, well-structured documentation.

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 reporting tool with no output schema and 3 parameters, the description covers the main action and the most important parameter. It doesn't explain return values, but that's not critical for such a tool given its annotations. The description is complete enough for the AI to understand what the tool does and how to use it properly, though a bit more detail on response handling could make it a 5.

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 schema has no descriptions for the parameters (0% coverage), so the description should compensate. It clarifies the 'conversation' parameter by stating it should include recent messages for reproduction, but it doesn't explain 'message' (the required field) or 'context'. Thus, it partially adds meaning beyond the schema but doesn't fully compensate for the missing schema descriptions.

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 combination that distinguishes it from sibling tools like authenticate, marketplace, or show_version, which serve entirely different functions.

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 when to use the tool (when reporting bugs, missing features, or feedback) and even gives guidance to include the conversation array for reproduction. However, it doesn't explicitly mention alternatives or when not to use it, which would be a 5. Still, the context is clear and there are no conflicting reporting tools among the siblings.

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