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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral context beyond those: the data is public/non-confidential, available to citizens from Brazilian official agencies, and the client is the LGPD controller. This clarifies the operational and legal nature of the query.

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 three sentences with useful information packed in: purpose, hosting, billing, data provenance, and LGPD responsibilities. It is somewhat dense but contains no meaningless filler and front-loads the tool's core purpose.

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 simple read-only query with one parameter, the description covers purpose, data source, credentials, payment, and legal context. However, with no output schema, it does not indicate what the response contains or any matching behavior (e.g., exact vs. partial match on razao_social), leaving minor gaps.

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 input schema has one required string parameter, razao_social, but schema_description_coverage is 0%. The description never mentions or explains this parameter, so the agent must infer meaning from the parameter name alone. The name is fairly self-evident, but the description does not compensate for the lack of schema documentation.

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 a specific action ('consulta') and resource ('Empresas' via SUSEP in an official source), which distinguishes it from the unrelated sibling tools. It could be more precise about exactly which company data is returned, but the core purpose is unambiguous.

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 useful context: it uses official sources, requires no platform credentials, and is paid via prepaid credits. However, it gives no explicit guidance on when to choose this tool over alternatives or when not to use it, and sibling tools are not referenced.

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