entradas_recentes

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

No annotations are provided, so the description carries the full burden. It discloses an important behavioral nuance: entry dates may be approximate (±1 day) depending on whether the SPA exposes full tooltips. It also states the ordering behavior. This adds meaningful context beyond the schema, though it doesn't discuss pagination or limits.

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 two sentences, front-loaded with the core purpose and ordering, followed by a concise explanation of date precision. Every sentence adds value without unnecessary detail.

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?

An output schema exists, so return values don't need explanation. However, the description omits the meaning of the required parameter flow_id and the optional limite, which are part of the tool's correct invocation. The date precision nuance is helpful, but the tool is not fully described for correct use.

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 0%, so the description must explain all parameters. It explains 'dias' (time window and date precision) but does not clarify the required 'flow_id' (likely the box identifier) or 'limite' (record limit). This leaves critical parameters undocumented for the agent.

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: lists processes that entered a SPA box within a time window, ordered newest to oldest. This clearly distinguishes it from siblings like 'listar_caixa' (likely current contents) and 'buscar_processo' (search by criteria).

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 usage for retrieving recent arrivals, but it does not explicitly state when to use this tool versus alternatives like listar_caixa or buscar_processo. No exclusions or alternative recommendations are provided.

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