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

No contradiction with annotations (readOnlyHint=false, idempotentHint=true). It adds the reproduction context, but does not disclose side effects, external transmission, or authentication needs; the annotations carry some of the safety profile.

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 precise sentences, front-loaded with purpose and an actionable instruction. 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?

For a simple three-string-parameter tool with no output schema, the description covers the core purpose and the key reproduction requirement. It could be more complete by explaining the required message parameter and the optional context parameter.

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 explains conversation's role for reproduction, but leaves message and context semantics undefined, and there are no parameter-level descriptions.

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?

States 'Report a bug, missing feature, or send feedback' – a specific verb and resource. This clearly differentiates it from siblings like authenticate, marketplace, and tribunal_trf1_certidao_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?

Explicitly says when to use it (bug, missing feature, feedback) and instructs to include the conversation array for reproduction. It does not name exclusions or alternatives, but the sibling tools are obviously unrelated.

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