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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the bulk support behavior (accepts ids for batched execution) which is useful beyond annotations. No contradiction found.

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 very short and front-loaded with the main purpose. The bulk support note is a single additional sentence. No wasted words, though it could be slightly more structured with parameter explanations.

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?

Given 4 parameters with 0% schema coverage and no output schema, the description is incomplete. It does not explain the 'query' and 'account' parameters, nor does it describe the return format or any pagination/limitations. For a GET tool with bulk support, more detail is needed for correct 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%, so the description must compensate. It mentions 'id' implicitly via the endpoint and 'ids' for bulk, but does not explain 'query' or 'account' parameters at all. The description adds minimal meaning beyond the schema for two of four parameters, leaving the other two unexplained.

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 'Campos extras de cadastros: Visualizar (GET /api/atributos_cadastros/{id})' which clearly indicates a GET operation to view extra fields of registrations. It distinguishes from siblings by the resource type (atributos_cadastros) and the GET verb, though it doesn't explicitly contrast with the list tool.

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 implies usage for viewing specific extra fields by ID, and mentions bulk support via 'ids'. However, it does not explicitly state when to use this vs. the list tool or other get tools for different resources, nor does it mention any exclusions or prerequisites.

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