senado_ecidadania_obter_consulta

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by specifying the exact return fields and noting that some fields may be null. It does not discuss rate limits or authentication, but annotations cover the safety profile adequately.

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 paragraph that efficiently conveys purpose, parameters, and return format. It is front-loaded with the main action but could be broken into multiple sentences for improved readability. However, there is no superfluous information.

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?

With an output schema present, the description explains the tool's return object fields, parameter source, and notes about nullable fields. For a simple retrieval tool, this covers all necessary context 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 100% with a single required parameter 'id' described as 'ID da consulta pública'. The description adds context by explaining that the id comes from specific sibling tools, and also mentions the return structure, which helps infer the parameter's purpose.

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 retrieves details of a specific public consultation from e-Cidadania, with a specific verb ('Obtém') and resource. It lists the return fields, distinguishing it from sibling tools like senado_ecidadania_listar_consultas and senado_ecidadania_consultas_analise.

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 explicitly instructs to obtain the 'id' parameter via senado_ecidadania_listar_consultas or senado_ecidadania_consultas_analise, providing clear prerequisite guidance on when to use this tool.

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