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

Annotations already indicate non-read-only, non-destructive, idempotent behavior. The description adds useful context by instructing users to include the conversation array for reproduction, but it does not disclose side effects such as whether a ticket is created or what happens after submission.

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-loaded with purpose and followed by a key usage instruction. There is no filler or redundant content.

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 is simple and the description covers its primary purpose and the important reproduction instruction. However, with no output schema, it does not mention what the agent should expect after reporting (e.g., confirmation, response format), and the 'context' parameter remains unexplained.

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 compensate. It only clarifies the 'conversation' parameter (array with recent messages); 'message' and 'context' are left to their schema names, and no format or usage details are provided for them.

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 uses a specific verb ('Report') and clear objects ('bug, missing feature, or send feedback'), making the tool's purpose immediately obvious. It also distinguishes itself from sibling tools like authenticate, toolkit_info, and tribunal_tjsp_segundo_grau_consultar.

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 gives clear context for when to use the tool: to report a bug, request a missing feature, or send feedback. It does not explicitly name alternatives or exclusion cases, but there is no sibling tool with overlapping purpose.

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