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

Annotations already indicate readOnly=false and idempotent=true. The description does not add context about what happens after reporting (e.g., ticket creation, data transmission) or clarify the idempotent behavior. It does instruct on submitting conversation data, which adds some transparency, but falls short of describing the full behavioral implications.

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 redundancy. It front-loads the purpose and then adds a single actionable instruction, making it 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?

The description covers the core usage but omits details about what happens after submission and leaves parameter semantics under-explained. Since there is no output schema, the return behavior is also unspecified. While adequate for a simple tool, it could be more complete given the zero-coverage schema.

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 zero description coverage, so the description must compensate. It only mentions the conversation array, providing a hint about its purpose, but does not explain the 'message' or 'context' parameters. The format of the conversation array (string containing a JSON array) is also not clarified, leaving ambiguity.

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 a specific verb 'Report' and three supported intents (bug, missing feature, feedback). It is distinct from sibling tools, none of which are related to issue reporting. The instruction to include the conversation array further clarifies the scope.

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 for when to use the tool (any bug, missing feature, or feedback) and explicitly instructs to include the conversation array for reproduction. It does not mention alternatives or exclusions, but since sibling tools are unrelated, the guidance is sufficient without needing explicit exclusions.

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