Somar dias úteis a uma data

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful behavioral context by specifying that the initial day is not counted, negative N moves backward, and different calendars apply.

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?

The description is three tight sentences with the core calculation rule front-loaded, followed by use cases and the key alternative. There is no filler.

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 six-parameter date calculation tool with full schema coverage and no output schema, it covers the counting convention, calendar domain, use cases, and main alternative. It does not explicitly state the return value format, which leaves a minor gap for invocation clarity.

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 100%, so the baseline is 3. The description still adds important meaning not fully captured in the schema by emphasizing the exclusion of the initial day and reinforcing negative N and the calendar choice.

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 states a specific operation: return the date that falls N business days after or before a given date, excluding the starting day, under forensic, national, or banking calendars. It also distinguishes itself from the sibling calcular_prazo for procedural deadlines arising from intimation.

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?

It gives explicit use cases (internal office deadlines and bidding deadlines) and explicitly redirects procedural deadline calculations from intimation to calcular_prazo. The alternative is named with the condition that selects it.

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