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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description's job is lighter. It adds useful behavioral context by describing the full response shape, including the conditional normaGerada field and the current state fields, and by noting the workflow prerequisite that the id comes from another tool. There is no contradiction with the 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 front-loaded with the core purpose and then moves to return content and routing guidance. It is dense rather than bloated, though the long field enumeration could be trimmed if the output schema already documents the response object. Overall, every sentence serves a clear role.

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 single-parameter, read-only tool with annotations and an output schema available, the description covers the essential invocation context: what the tool returns, where the id comes from, and which sibling should be used for related but different details. It does not discuss error behavior for nonexistent ids, but that is not a critical gap for this simple read operation.

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%, so the baseline is 3; the description adds value by explaining that the parameter is obtained from senado_search_processos or senado_buscar_materias and by clarifying the practical meaning of the id. It does not fully resolve the minor mismatch between the description's 'id' and the schema's idProcesso, but it later uses the correct name.

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 ('Obtém') and resource ('um processo legislativo específico pelo seu id'), and explicitly distinguishes itself from senado_processo_detalhe by saying that emendas, relatorias, and prazos are handled there. This makes the tool's identity and scope immediately 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?

It gives explicit prerequisites ('Obtenha o idProcesso antes via senado_search_processos ou senado_buscar_materias') and names the alternative for overlapping concerns ('para emendas, relatorias ou prazos use senado_processo_detalhe'). The agent is told exactly when and how to route around sibling tools.

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