Cálculos recentes no PJe-Calc

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful scope context (it is the home-screen recent list, not an arbitrary query) and the returned fields, but says nothing about ordering, limits, or empty-state behavior.

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, front-loaded sentence with no waste. The nested quotation of the UI label is slightly noisy but does not obscure meaning or bloat the text.

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 zero-parameter, read-only listing tool with annotations covering safety, the description covers purpose and output fields adequately. The absence of an output schema means some details (result structure, ordering, count limits) remain unspecified, leaving a modest gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate, per the baseline-4 rule. The parenthetical field list adds minor value about what the (parameterless) call yields but is not required.

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 ("Lista") and resource ("Cálculos Recentes" / aba Abrir Cálculos Recentes do PJe-Calc), and names the fields shown. It distinguishes the tool from sibling readers like calculo_ler_pjc or pjecalc_paginas, though the reliance on a UI label rather than a functional description slightly muddies it.

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?

No explicit when-to-use, when-not, or alternative routing is provided. The agent can only infer that this browses recently opened calculations; nothing tells it how this differs from calculo_ler_pjc or calculo_pendencias in a selection scenario.

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