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

Annotations confirm it is safe and read-only. The description adds crucial behavioral detail by specifying the calculation methodology (e.g., Ecuador: SRI 2026 tables; Paraguay: IRP brackets) and the expected output (official sources/links).

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 highly concise and efficient, managing the complexity of two different national tax systems into one cohesive and front-loaded paragraph.

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?

Given the inherent complexity of modeling two separate, real-world annual income tax systems, the definition is complete. It covers rules, scope, calculation methods, and even expected output (links/sources).

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%, meeting the baseline. However, the description significantly adds value by contextualizing the parameters within the specific tax logic (e.g., defining 'cargas' as family benefits/rebates for Ecuador and outlining deducible expenses for Paraguay).

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 purpose is perfectly clear: calculating the annual income tax for employed workers. It distinguishes itself by explicitly naming the dual scope (Ecuador 2026 SRI tables vs. Paraguay IRP brackets).

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 defines a clear use case (annual tax calculation based on specific national rules). While it doesn't list all alternatives, its highly specific domain distinguishes it implicitly from sibling payroll calculation tools.

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