listar_intimacoes

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly states 'Operação SOMENTE LEITURA - sem efeito jurídico', discloses that secret-justice intimações have suppressed content, and lists required credentials. It does not cover pagination or error handling, but the disclosed traits are meaningful and not redundant.

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 main purpose and read-only safety notice, followed by return behavior and a compact bulleted credential list. There is no redundant or filler text, and each sentence contributes essential 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?

The description is complete for an agent to invoke the tool correctly: it explains the operation's read-only nature, the credential requirements, the filtering context, and the secret-justice special case. Since an output schema exists and the input schema is fully documented, nothing critical is missing.

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 description coverage is 100%, so all three parameters (limite, numero_processo, apenas_pendentes) are already documented with defaults and examples. The description does not add parameter-level semantics beyond the schema, though it adds useful environment-variable context for authentication. A baseline 3 is appropriate.

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 and resource: 'Lista comunicações processuais do Domicílio Judicial Eletrônico (DJe)', and clarifies the scope by enumerating intimações, citações e notificações. The focus on DJe communications and the read-only qualifier make it distinguishable from siblings like listar_movimentacoes and confirmar_leitura_intimacao.

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 clearly conveys that this is the read-only listing operation for DJe communications and specifies the required credential environment variables. It does not explicitly state when to prefer an alternative or when not to use this tool, so it falls short of a 5.

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