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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real value beyond that by disclosing that the result is an interactive card with adjustable values and that it returns sources and assumptions. It stops short of describing whether values are estimates only or how rounding/versioning of tax tables is handled.

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?

Three short sentences, zero filler: what it does, what it requires, what it accepts, what it returns. The required input is called out early and nothing is repeated.

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 an output schema present, the description needn't explain return values, yet it still flags sources and assumptions, which is helpful for a financial estimate. The remaining gap is sibling disambiguation against calcular_salario_liquido and the default for dependentes, but for a 4-parameter read-only tool this is close to complete.

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 75% and the description enumerates all four inputs by name, explicitly marking salarioBruto as required and grouping the three optional ones (dependentes, vale-transporte, dias úteis). It does not add units or defaults beyond what the schema already states, so it complements rather than extends the schema.

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+resource ('Calcula e apresenta salário líquido estimado') and adds the delivery form ('cartão interativo com os descontos detalhados e valores ajustáveis'). However, it never distinguishes itself from the near-identically named sibling calcular_salario_liquido, which is the exact confusion an agent must resolve.

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 one prerequisite ('Requer salário bruto informado') and enumerates the optional inputs, which implies the calling context. But it offers no when-to-use/when-not guidance and does not name calcular_salario_liquido as the alternative, so an agent choosing between two net-salary tools gets no routing help.

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