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

Annotations already declare readOnly, idempotent, non-destructive; the description adds meaningful context: platform-hosted, no credentials, pay-per-query with prepaid credit, public-access data only, and LGPD data-controller responsibility. No contradiction with 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 three sentences, front-loaded with the main purpose, followed by access/payment and legal context. It is reasonably tight, though the LGPD sentence adds length without operational detail.

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?

No output schema and no parameter explanations leave gaps: the agent cannot know what NodeID refers to, what completo controls, or what the result looks like. The description covers purpose and data nature but not enough operational detail for confident invocation.

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 NodeID, Nome, or the optional completo boolean. The only indirect hint is 'verifica se um nome aparece', leaving required parameters ambiguous for invocation.

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 tool checks whether a name appears in the ICIJ Offshore Leaks database (offshore structures), with explicit compliance/AML purpose. This specific verb+resource distinguishes it from the unrelated sibling tools (authenticate, marketplace, etc.).

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 frames usage for compliance and AML due diligence, states no credentials are needed and queries are paid with prepaid credit, and clarifies the data is public rather than private/confidential. It does not name explicit alternative tools or when-not-to-use scenarios, but the context is clear enough.

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