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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the agent knows this is a non-destructive, idempotent write operation. The description adds little beyond purpose and doesn't disclose side effects, permissions, or post-submission behavior, but it doesn't contradict 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?

A single sentence that states the exact purpose and includes a key usage detail. No redundant words, no rambling, and the most important information is front-loaded.

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 straightforward feedback/report tool, the description covers the core action and the reproduction hint. It doesn't mention output or what happens after submission, but no output schema exists and the annotations cover basic behavior. This is adequate for the simplicity of the tool.

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 carries the full burden for parameter meaning. It explains the 'conversation' parameter by asking for the array of recent messages, but the schema type is actually 'string' (likely JSON-encoded), which is slightly misleading. The required 'message' parameter and the optional 'context' parameter are not described at all.

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 opens with the specific action 'Report a bug, missing feature, or send feedback', clearly identifying the tool's purpose. It also mentions the key input (conversation array) and is distinct from unrelated siblings like authenticate, connect, and tribunal_tjrs_primeiro_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 instruction to include the conversation array with recent messages for reproduction provides clear usage context. There are no explicit exclusions or alternative tool comparisons, but the sibling set is unrelated, so this level of guidance is reasonable.

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