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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds that this is a GET endpoint and supports batched ids, but it does not mention authentication needs, rate limits, response shape, or any other execution behavior.

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?

Two short lines contain the required entity, the HTTP endpoint, and the bulk capability. No filler, repetition, or unnecessary details.

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 read-only tool with strong annotations, the description is decent but still incomplete: there is no output schema, and several parameters are not described. An agent would need to infer the roles of 'query' and 'account' from the raw property names.

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 description explains the core 'id' semantic and indicates 'ids' is for batch execution, which adds value over bare property names. However, schema description coverage is 0% and the 'query' and 'account' parameters remain unexplained, leaving meaningful gaps.

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?

Clearly states 'Buscar negócio por ID' (find business by ID) and gives the REST endpoint. The bulk support differentiates this from a plain single-get and from sibling list/patch/create tools.

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 when one business ID is available, but it does not explicitly say when to use this instead of datacrazy_businesses_list or when to prefer batch ids over a single id. There is no when/when-not guidance.

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