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

Annotations already mark the operation as a write, and the description adds that it adjusts stock in a batch via a specific POST endpoint. It does not clarify side effects like whether partial batches succeed, whether stock values are overwritten, or what the response contains, so the behavioral picture is incomplete.

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 concise: one sentence covering purpose, the HTTP endpoint, and the primary parameter. There is no filler, and the most important information is front-loaded.

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 that there is no output schema and annotations are minimal, the description should carry more weight. It omits the structure of a 'ajuste' object, the meaning of `account`, and any return/error behavior, making this a recognizing statement rather than a fully actionable tool definition.

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 adds semantics only for `data` ('array de ajustes'), which is valuable because the schema itself provides no descriptions. However, the `account` parameter is completely undocumented, and the schema types `data` as a string rather than an array, creating ambiguity about the actual input format. The description only partially compensates for 0% schema coverage.

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 is specific: 'Ajusta o estoque de produtos em lote' clearly identifies the action (adjust), the resource (product stock), and the mode (batch). It also cites the exact POST endpoint, and it is distinguishable from sibling tools like mercos_create_produto, mercos_update_produto, and mercos_list_produtos.

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 phrase 'em lote' implies this tool is intended for bulk stock adjustments, giving some usage context. However, it does not explicitly state when to prefer this over alternatives such as mercos_update_produto, and it offers no exclusion criteria like 'use for multiple products only'.

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