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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds substantial behavioral detail beyond annotations: it analyzes the complete set of open consultations and ideas, filters by polarization/consensus and minimum participation, returns at most 10 suggestions sorted by participation, and clarifies that count differs from totalQualificados. It also reveals that apenasEmTramitacao considers real status of consultations. No contradiction exists.

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 but front-loaded: it opens with the tool's core purpose, then details the output contract, criteria defaults, and follow-up actions. Every sentence contributes useful information for selecting and invoking the tool correctly, with no filler or repetition of the title.

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?

Given the tool's complexity—nested optional criteria, rich output, and many siblings—the description is complete. It explains input semantics, output fields and limits, ordering, the difference between count and totalQualificados, and how to investigate returned suggestions. Annotations cover safety and idempotence, and an output schema exists, so no critical context is missing.

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 100%, so the baseline is 3. The description adds value by explaining the optional criteria object's defaults and behavior, especially clarifying that apenasEmTramitacao 'considera só consultas abertas, com base no status real' and that minimoParticipacao defaults to 500. This goes beyond the schema's short field descriptions, though the schema already carries most parameter meaning.

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 and resource: 'Sugere temas para uma enquete pública mensal' by analyzing e-Cidadania consultations and ideas and electing the most engaging ones. It clearly explains the tool's selection role and distinguishes it from list/obtain siblings by framing this as an analytical suggestion tool with a ranked output.

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 provides clear usage context: it is for selecting public poll themes and returns suggestions for further investigation. It explicitly routes follow-up behavior with 'Para investigar uma sugestão, use senado_ecidadania_obter_consulta ou senado_ecidadania_obter_ideia conforme o tipo.' However, it does not explicitly state when not to use this tool versus sibling analysis/list tools, so it falls short of a 5.

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