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

The description mentions a specific behavior: including the conversation array for reproduction. It does not detail side effects, but the annotations already confirm idempotent and non-destructive behavior, so the description adds a useful hint about the input's role without contradicting the 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 concise and well-structured: two sentences that state the purpose and provide a key instruction. No redundant or vague language.

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, the description covers the core purpose and a critical input detail. It does not explain what happens after reporting or expected response format, but given the low complexity, it is reasonably complete.

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 provides no descriptions for the three parameters, and the description only elaborates on the 'conversation' parameter (for reproduction). It does not clarify the meaning of 'message' (likely the bug description) or 'context', leaving the agent with incomplete understanding of required inputs.

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: reporting bugs, missing features, or feedback. It specifies the action ('report') and the target (bug/feature/feedback), making it distinct from sibling tools like 'authenticate' or 'consult'.

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 implicitly defines when to use it: when the user has a bug, missing feature, or feedback. It does not explicitly mention alternatives or exclusions, but the use cases are clear enough for an agent to choose this tool over others in the context.

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