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

Annotations already cover idempotency and non-destructive behavior. The description adds context that the conversation details are used for reproduction, but it does not disclose side effects (e.g., data delivery method, whether a response is expected) or any other operational nuances. No contradiction with 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?

Two concise sentences front-load the purpose and then give one necessary usage note. No redundant language or repetition of schema-field names.

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 3-parameter tool with no output schema, this description is minimally adequate. It says what the report is and how to improve reproducibility, but omits guidance for the 'context' parameter and does not describe what happens after submission or any possible errors.

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 clarify all parameters. It partially explains 'message' by implication (bug/feedback text) and 'conversation' by telling users to include recent messages, but it leaves 'context' completely undefined and does not specify formats or examples for conversation beyond 'array'.

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 exact purpose: 'Report a bug, missing feature, or send feedback.' This is specific and distinct from all sibling tools, which cover unrelated actions like authenticate, connect, and marketplace.

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?

It provides clear user-facing context for when to use the tool (bug, missing feature, feedback) and even gives a usage hint about including the conversation array. However, it does not explicitly discuss when not to use it or compare with alternatives, though none of the siblings compete.

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