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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral context: per-query cost with prepaid credit, absence of platform credentials, official/non-confidential data status, and LGPD data-controller responsibilities. It does not cover response behavior, rate limits, or pagination, but it goes well beyond the annotations.

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 compact and front-loads the main purpose before adding operational and compliance details. Each sentence contributes useful context, though the legal/operational phrasing could be tightened. Overall it is appropriately sized.

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 six required parameters, no output schema, and no parameter descriptions, the tool demands more explanation than this description provides. The operational and LGPD context is useful, but the absence of parameter details and return-value description means an agent cannot confidently invoke it correctly.

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 0% and the description does not explain any of the six required parameters (cnpj, tipo_declaracao, ano_calendario, receita_bruta_comercio, receita_bruta_servicos, possui_empregado). The SIMEI context only indirectly hints at their meaning, which is insufficient for an agent to know expected formats or valid values.

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 identifies a consult operation on official Receita Federal SIMEI annual declaration data ('SIMEI (Declaração Anual), consulta em fonte oficial'). It gives a specific verb and resource, and it is distinct from generic platform siblings. However, it does not specify exactly what data is returned or fully explain the DASN relationship beyond the name.

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 operational prerequisites: no platform credentials are needed, prepaid credit is required per query, and the data is non-confidential. This implies when the tool can be used, but there is no explicit comparison with alternatives or when-not-to-use guidance. Sibling tools are unrelated, so the usage context is only implied.

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