Atualizar precatórios SIP (REST)

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

Annotations already declare the safety profile (write, destructive, idempotent, closed-world). The description adds the batch nature, the returned processed list, and the runtime dependency (app must be running), which are genuine additions. It does not explain what the update destroys or the DTO's mutation semantics, so with annotations carrying the burden a 3 is appropriate.

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?

A single compact sentence front-loads the endpoint, then the action, the return, and the runtime requirement in sequence. No filler text; every clause carries 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?

For a one-parameter batch mutation with no output schema, the description covers endpoint, batch action, return value, and runtime dependency. The DTO shape is only referenced rather than described, but that is acceptable given the schema and lacks an output contract to explain.

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% for the single 'lista' parameter, so the schema already documents it. The description restates that the list holds AtualizacaoPrecatorioSIPDTO objects but adds no syntax or format detail beyond the schema, giving the baseline 3.

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?

States a specific verb and resource: batch-updates a list of AtualizacaoPrecatorioSIPDTO (SIP precatórios) via a named REST endpoint. The 'em lote' / 'SIP' qualifiers provide some differentiation from the singular sibling rest_precatorio_atualizar, though it never names that sibling explicitly.

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?

Provides one prerequisite ('Requer o app em execução'), which is useful context. However, it gives no explicit when-to-use guidance relative to alternatives like rest_precatorio_atualizar or rest_precatorios_sip_indices, leaving routing to inference.

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