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 covered. The description adds only the HTTP method, but nothing about response format, filtering behavior, pagination, or any side effects beyond what annotations imply. It does not contradict annotations, but adds minimal behavioral context.

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 extremely short, one sentence, with no fluff. However, its brevity is not justified because it omits essential information about parameters and usage. It is under-specified rather than appropriately concise.

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 list operation with two undocumented parameters and no output schema, the description should explain the query and account parameters and any filtering semantics. It only states the endpoint and a generic verb, leaving the agent without sufficient information to invoke it correctly. This is inadequate for a tool with this complexity.

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 mention the 'query' or 'account' parameters at all. There is no explanation of what these parameters mean, their formats, or how they affect the search. Since these are the only parameters, this is a severe gap.

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 'Buscar instancias' (Search instances) clearly indicates it lists instances, and the endpoint GET /api/v1/instances confirms the action. However, it does not differentiate from the sibling datacrazy_instances_get, which retrieves a single instance, so it lacks explicit scoping or uniqueness guidance.

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?

There is no guidance on when to use this tool versus alternatives such as datacrazy_instances_get. No mention of conditions, prerequisites, or when not to use it. The description provides no context for selection.

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