prazos_urgentes

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

With no annotations, the description carries the burden of explaining behavior. It discloses the interpretation of 'prazo vigente' (the closest future date from a field that accumulates historical deadlines) and clarifies that negative remaining days indicate overdue processes. This is meaningful context beyond the basic purpose.

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 concise, with three sentences that front-load the main purpose and then provide necessary detail about the deadline logic. There is no wasted wording, and the structure is logical.

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 covers the core scanning behavior, ordering, and the vigente calculation, and mentions the output field `prazo_completo`. However, it omits explanations for two of the three parameters and does not describe pagination or edge cases, leaving the tool only partially specified.

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 0%, so the description must explain the parameters. It clearly explains `dias` (the lookahead window) but leaves `por_fluxo` and `incluir_atrasados` completely unexplained, creating a significant gap for a tool with only three parameters.

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 scans all user boxes and returns processes with deadlines within the next `dias` days, sorted by urgency. The action and resource are specific, though it does not explicitly differentiate from sibling tools like listar_caixa or buscar_processo.

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 implies when to use this tool (to find processes with upcoming deadlines) but does not provide explicit guidance, exclusions, or alternatives. It does not mention when not to use it or which sibling tool would be preferable in other scenarios.

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