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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds valuable context: it is hosted on the platform, requires no credentials, involves per-query payment, and clarifies that data is not confidential and is subject to LGPD. This goes beyond the annotations, though it does not detail any other side effects.

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 relatively concise but repetitive, using phrases like 'consulta' and 'oficial' multiple times. It is structured as a few sentences but lacks clear organization. Some redundancy exists, such as repeating 'consulta informação de fontes e órgãos oficiais' after the initial statement. It could be tightened without losing meaning.

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?

The description provides useful context about the data source (official Brazilian bodies), its status as non-confidential, and legal considerations (LGPD). However, it does not describe what information is returned by the query, which is a significant gap for a lookup tool. Since there is no output schema, the description could have elaborated on the expected result. Overall, it gives some context but leaves the functional output unspecified.

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 schema lists three parameters (cpf, cnpj, birthdate) with no descriptions. The description does not explain their purpose or format. While one might infer that cpf and cnpj are Brazilian tax identifiers and birthdate is for individual verification, this is not explicit, leaving users to guess. The description also does not clarify which parameter is required beyond the schema's 'required' field.

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's function: consulting the Declaração de Aptidão ao PRONAF (DAP) from official Brazilian sources. The verb 'consultar' and the resource 'DAP' are specific, and it distinguishes itself from sibling tools by focusing on this particular data lookup.

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 does not provide explicit guidance on when to use this tool versus alternatives. It mentions payment and legal aspects but lacks context on typical use cases or distinctions from other tools like 'authenticate' or 'connect'. No alternatives are referenced, leaving the usage scenario implicit.

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