Feriados e pontos facultativos

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that this is static PJe-Calc catalog data tied to calculo.pontosFacultativos, but says nothing about return format, ordering, or pagination. Adequate but not rich.

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 dense sentences with no filler, and the core resource definition is front-loaded before the ancillary note about calculo.pontosFacultativos. Efficient for the amount of information conveyed.

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 read-only catalog lookup with no output schema and fully documented parameters, the description explains what data comes back and how it relates to the calculation. Only the return shape and filtering behavior are left implicit, which is a minor 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?

Schema description coverage is 100%, so the schema already documents uf, tipo, filtro and municipio, establishing the baseline of 3. The description restates the tipo F/P meaning and adds the F/E/M abrangência taxonomy, which actually refers to holiday records rather than a parameter and omits the schema's third enum value 'B'. Marginal added value.

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 names the exact resource (feriados tipo F and pontos facultativos tipo P from PJe-Calc) and its scope (national/state/municipal). An agent can tell it apart from sibling catalogs like catalogo_municipios or catalogo_verbas. It never states an explicit verb such as 'list/retrieve', but the catalog nature is clear.

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 guidance on when to call this versus sibling catalogs, and no prerequisites. The only contextual hint is that pontos facultativos are marked in the calculation by name in calculo.pontosFacultativos, which describes downstream use rather than when to invoke this tool.

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