listar_intimacoes

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

No annotations provided, so description carries full burden. It discloses read-only nature, secret justice suppression, and required credentials. However, it lacks details on rate limits, error behavior, or pagination beyond the limite parameter.

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 reasonably concise, front-loading purpose and read-only warning. Every sentence adds value, though the credential list could be slightly shorter if integrated.

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?

Output schema exists, so return values need not be detailed. The description covers read-only nature, secret justice, and credentials, but misses pagination behavior, ordering, or what recent means for default limite.

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 good parameter descriptions. The overall description adds minimal additional semantics for parameters beyond the schema, but the credential environment variables are helpful context.

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 communications from DJe (intimações, citações, notificações) and specifies it is read-only. It distinguishes itself from siblings like confirmar_leitura_intimacao by explicit read-only nature, though not referencing siblings directly.

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 says it is a read-only operation but does not explicitly guide when to use this tool versus alternatives like confirmar_leitura_intimacao or listar_processos_monitorados. Usage context is implied but not contrasted.

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