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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds that the conversation array is needed for reproduction, which hints at how data is used. Beyond this, no additional behavioral traits are disclosed, but given the annotation coverage, the description is adequate but not rich.

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 compact sentences, no filler. The first sentence establishes purpose, the second provides a key usage instruction. Every word adds value.

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?

The tool has three parameters and no output schema, making it relatively simple. The description covers the primary purpose and one parameter's role, but lacks explanation for 'message' and 'context'. It is adequate for basic use but leaves gaps for proper parameter 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?

The schema has 0% description coverage, so the description must compensate. It only mentions the conversation parameter ('conversation array with recent messages'), leaving 'message' and 'context' unexplained. Without details on what message should contain or how context is used, the parameter semantics are notably incomplete.

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 with the verb 'report' and specifies three distinct use cases: bug, missing feature, or feedback. It also includes an instruction about the conversation array, which adds specificity. However, it does not explicitly differentiate from sibling tools, though the siblings are unrelated so confusion is unlikely.

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 on when to use the tool ('when you have a bug, missing feature, or feedback') and gives a usage hint ('include the conversation array'). It lacks explicit exclusions or alternative tool mentions, but the context is sufficiently clear.

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