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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does explain that the tool returns the 'active' default parameters and lists their categories, but it does not mention output format, potential side effects, or whether data might be cached or dynamically sourced.

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 a single, compact sentence that efficiently conveys the tool's purpose and content. There is no redundancy or filler, and the key information is immediately accessible.

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 parameterless getter, the description is reasonably complete: it identifies the returned data, its categories, and its usage context. Since there is no output schema, a bit more detail about the exact structure or format of the returned parameters would improve completeness, but the low complexity makes the current description adequate.

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?

The tool has zero parameters, so parameter-specific semantics are not needed. The schema confirms an empty object with additionalProperties false, and the description adds no unnecessary parameter commentary, which is appropriate here.

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 verb 'Retorna' and the resource 'conjunto ativo de parâmetros padrão brasileiros', specifying the content categories (taxas, prazos, custos) and its intended use by the site and simulations. This distinguishes it from the sibling calculation/comparison 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 implies the tool is relevant when defaults are needed for site behavior or simulations, but it does not explicitly state when to use it instead of alternatives like get_municipio_rates or get_site_info. No exclusions or direct sibling comparisons are provided.

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