calcular_plazo

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

With no annotations, the description carries the full transparency burden. It discloses the counting logic (3 business days, skipping weekends and court holidays) and explicitly states the output (the date when the deadline period begins). This exceeds basic expectations, though it could mention edge-case behavior for invalid dates.

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 concise, three sentences long, and front-loaded with the primary action. Every sentence contributes: what it does, the legal rule, and the return value—no superfluous information.

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 simple one-parameter tool with no output schema, the description is complete. It covers the legal basis, calculation rule, and return value, and given the sibling context, it is clear when to use this tool.

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 schema already documents the format. The description adds meaning by framing the parameter as a 'notification date' and explaining its legal significance, which helps the agent understand what to pass and why.

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 clearly states the tool's function: it calculates the first day a procedural deadline begins, given a notification date. It specifies jurisdictional context (Cordoba, Argentina) and the exact rule (3 business days forward, skipping weekends and court holidays), distinguishing it from sibling getter tools.

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 provides clear context: use when you have a notification date (typically from a cedula) and need to know when the deadline period starts. It does not explicitly name alternatives or exclusions, but the sibling tools are all read operations, making the use case evident.

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