senado_discursos_senador

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

Discloses return format including structure with `codigoSenador`, `tipo`, `count`, `discursos`, and that full text is not included. Adds value beyond the `readOnlyHint` and `openWorldHint` annotations by detailing output limitations.

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 dense sentence that front-loads the main action and includes all key information. It is efficient, though slightly more structure could improve readability.

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 tool with 5 parameters, an output schema, and connections to other tools, the description fully covers what it does, how to use it, what it returns, and how it fits into the ecosystem. No gaps remain.

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 each parameter described. Description adds minor context on `tipo` and filter options, but does not significantly enhance the parameter semantics beyond the schema's own 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?

The description clearly states it lists speeches of a senator with filters, and the `tipo` parameter distinguishes between own speeches and interventions. This differentiates it from siblings like `senado_discursos_plenario` and `senado_discurso_texto`.

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 instructs to obtain `codigoSenador` via `senado_listar_senadores` and to use `codigo` in `senado_discurso_texto` for full text. Provides clear context on how to use the tool, though it doesn't specify when not to use it.

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