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

Annotations include idempotentHint=true, destructiveHint=false, readOnlyHint=false, openWorldHint=false. The description doesn't contradict annotations. It adds that the tool includes conversation for reproduction, but it doesn't disclose details like what happens after submission (e.g., confirmation, rate limits). Given the annotations cover safety (idempotent, non-destructive), a 3 is appropriate—some context added, 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?

The description is a single, compact sentence that conveys purpose and a key usage detail. It is front-loaded and wastes no words.

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 straightforward (reporting feedback), with no output schema and simple parameters. Annotations cover idempotency and non-destructiveness. The description is sufficient for basic use but could be improved by clarifying what 'context' might contain and the expected format for 'conversation' (e.g., JSON array string). It's a minimal but adequate description for a simple 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?

The schema has three parameters: message (required, string), context (string, default ''), conversation (string, default '[]'). Schema description coverage is 0%, so the description must compensate. The description mentions 'conversation array' and implies its purpose (for reproduction), but it doesn't explain 'message' or 'context' beyond the schema. Given low coverage, the description adds some value for 'conversation' but leaves 'message' and 'context' semantically thin.

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 a bug, missing feature, or feedback, and it mentions including the conversation array for reproduction. It distinguishes from siblings like 'show_version' or 'toolkit_info' which are informational, and 'sefaz_rr_nfce_consultar' which is a specific external query. However, it doesn't explicitly name alternative tools for feedback, so it's clear but not fully differentiated.

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 implies when to use this tool (when reporting a bug/missing feature/feedback) and gives a key guideline about including the conversation array. It doesn't mention when not to use it or suggest alternative tools for other purposes, but the context is fairly clear for a feedback tool.

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