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

Annotations already declare readOnly/idempotent/non-destructive; the description adds value beyond them by stating public authorship, sources, and hashes of discussions, that no credential is required, and that cursor continuation preserves history. A minor gap is that it doesn't clarify pagination limits or what 'hashes' contain, but the safety-relevant context is well covered.

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 dense and front-loads the read capability, but packs multiple concerns (resource enumeration, conditional rules, recommendation behavior, cursor usage) into a tight block. The 'Recomenda próximos assuntos' sentence introduces a second capability that dilutes focus, and the proximo_cursor naming slip costs clarity.

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?

An output schema exists, so return values needn't be explained, and the conditional parameter rules help. But with 8 parameters and only 25% schema coverage, four parameters (area, assunto, tema_id, limite) are effectively undocumented across both schema and description, leaving the definition incomplete for correct invocation.

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 coverage is only 25%, and the description usefully adds the conditional requirements (comentarios exige post_id, respostas exige duvida_id), which are not encoded in the schema. However, it leaves area, assunto, tema_id, and limite unexplained, and references 'proximo_cursor' while the actual parameter is named 'cursor', which is a confusing mismatch.

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 states a specific verb ('Lê') and enumerates the resources (publicações, comentários, perguntas, respostas) as well as a recommendation capability. It reads as a broad 'explore the community' endpoint and does not explicitly distinguish itself from siblings like buscar_duvidas or ler_duvida, but the resource list makes the scope clear.

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?

Usage is implied through the resource enumeration and 'Recomenda próximos assuntos por tema, termos e área', which hints at discovery use. However, the description never says when to prefer this tool over buscar_duvidas, ler_duvida, or participar_rede_social, leaving sibling selection to inference.

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