calcular_idade

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It doesn't state how the age is calculated (e.g., whether it accounts for leap years, time zones, or partial years), what the return format is, or what happens with future dates. Significant gaps for a tool with no annotation coverage.

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, efficient sentence that front-loads the core purpose. No wasted words, though it could benefit from a note on the expected output.

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?

With no annotations, no output schema, and only one parameter, the description is minimal. It doesn't explain the return value (e.g., integer years) or any constraints, which are important for correct invocation. The description is insufficient for a tool where the agent needs to know the output format.

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 the single parameter's format (YYYY-MM-DD). The description adds no extra semantic detail about the parameter, such as handling of invalid dates. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (Calcula) and resource (idade) with the input basis (data de nascimento). Clearly distinct from siblings like date_utils and competencia_utils. No further differentiation is needed given it's a narrow utility tool.

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 implies when to use it (when you have a birth date and need an age), but offers no explicit conditions, exclusions, or pointers to alternatives. Adequate but lacks guidance on edge cases like future dates or invalid formats.

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