senado_listar_comissoes

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

Annotations already indicate read-only and non-destructive behavior. The description adds that the endpoint only brings active commissions, regardless of the filter, and explains the return shape. No contradictions with annotations.

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 two sentences long, front-loaded with purpose and filters, then details return format and usage guidance. Every sentence is informative and concise, with no extraneous text.

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 simplicity (two optional parameters, output schema exists, annotations cover safety), the description fully covers purpose, usage, and return structure. It also links to sibling tools, making it complete for an agent to select and invoke correctly.

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 descriptions for both parameters. The description adds context by stating that the endpoint only returns active commissions, implying that the ativa filter is redundant if set to true, and that false yields empty. This adds practical meaning beyond the schema.

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 lists active commissions with filters for tipo and ativa, and specifies the return structure with fields like codigo, sigla, nome, tipo, casa, and ativa. It distinguishes itself from siblings by noting it is used to discover the sigla required by senado_obter_comissao and senado_reunioes_comissao.

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 says to use this tool to discover the sigla needed by senado_obter_comissao and senado_reunioes_comissao, providing clear contextual guidance. It also warns that the endpoint only returns active commissions, so setting ativa=false results in an empty list, which helps correct usage.

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