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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable context beyond these: it requires no platform credentials, is paid per query with prepaid credit, data is from official Brazilian sources and not confidential, and the client is the data controller under LGPD. This enriches the behavioral profile without contradicting 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 concise, with the key purpose stated in the first clause ('Conselho Regional de Odontologia SP: Cadastro, consulta em fonte oficial') and additional context in subsequent sentences. It avoids verbosity and unnecessary details, though the legal and payment info could be considered slightly tangential, it still fits in a compact paragraph.

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 tool with a single parameter and no output schema, the description covers payment, credential, and data sensitivity context, which is useful. However, it does not describe what the response contains (e.g., status, name, validity), nor does it mention any caveats like rate limits or caching. Given the lack of output schema, the agent has no information about expected return structure, so completeness is partial.

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 sole parameter 'inscricao' is not explained in the description at all; schema description coverage is 0%. The parameter name is self-explanatory (likely meaning registration number), but the description does not confirm its format, required pattern, or what value to pass. Since the description does not compensate for the missing schema documentation, the agent must rely on the parameter name alone, which is insufficient.

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 states 'Cadastro, consulta em fonte oficial' (Registration, query from official source), clearly indicating it's a query operation for registration data from an official dental council. The name 'cro_sp_cadastro_consultar' further specifies the CRO SP context, distinguishing it from unrelated siblings like 'authenticate' and 'marketplace'. However, it does not explicitly mention that the query is about dentists or what exact information is returned.

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 no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. It does state that the query is paid via prepaid credit and requires no platform credentials, which could imply strategic usage, but it does not explicitly advise when to invoke this tool or when to prefer another. No comparison to sibling tools is given.

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