Atualizar índices de precatórios SIP (REST)

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the batch nature ('em lote') and the app-running prerequisite, but says nothing about what gets overwritten, required auth, or error behavior for a destructive batch write.

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?

Two short sentences, front-loaded with the endpoint and the action, with the operational prerequisite last. Efficient, though the full URL path occupies space that adds little semantic value.

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 destructive batch mutation, the annotations plus schema plus the app-running note cover the essentials. Missing are consequences of the update (what indices change, reversibility) that an agent would want before invoking a destructive write.

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 baseline is 3. The description names the same DTO type the schema documents but adds no format, limits, or item-shape detail beyond it.

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 update of a list of AtualizacaoPrecatorioSIPIndicesDTO, with the REST endpoint spelled out. It is distinguishable from siblings like rest_precatorio_atualizar and rest_precatorios_sip, though it never explicitly says how it differs from them.

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 only contextual guidance is the prerequisite 'Requer o app em execução', which is genuinely useful but not a when-to-use rule. No alternatives or exclusion conditions are named, leaving the agent to infer when this tool is preferred over nearby precatório tools.

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