Valores aceitos (enums do PJe-Calc)

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds real behavioral context beyond the annotations by disclosing the argument-dependent branching (listing enum names vs entity enum fields), which an agent needs to invoke it correctly.

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 tightly written sentences, examples front-loaded, no filler. The reader gets the resource and both modes immediately.

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 two-param read-only lookup with no output schema, the description conveys what is returned at a useful level (enum names, entity enum fields). A note on the actual return shape would close the last gap, but nothing essential is missing.

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 already 100% with both params documented, but the description adds meaning the schema lacks: it clarifies that omitting 'nome' lists enum names, and that 'classe' scopes results to an entity's enum fields, with worked examples.

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 clear verb+resource: it retrieves the accepted enum constants for PJe-Calc fields, with concrete examples (IndiceMonetarioEnum, JurosEnum, etc.). This distinguishes it from other catalog tools like catalogo_verbas or catalogo_municipios, though the differentiation is implicit rather than stated.

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 explains the two invocation modes (no argument → enum names; 'classe' → enum fields of an entity), which effectively tells the agent how to steer the call. However it does not say when to prefer this tool over sibling catalogs or what prerequisites exist.

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