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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which covers the safety profile. The description adds the endpoint and a note that orders live in v2, but it does not disclose pagination behavior, return format, or rate limits, so it contributes only moderate 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 concise: one short sentence plus a parenthetical, with no filler or repetition. It front-loads the core purpose and immediately follows with a practical usage hint.

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 list tool with good annotations and no output schema, the description is minimally adequate but leaves gaps: no mention of return values, pagination, or the meaning of 'account' and 'filters'. It provides enough for basic invocation but not full self-sufficiency.

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 only explains 'alterado_apos' (for incremental updates) but leaves 'account' and 'filters' entirely undocumented, which is insufficient for a tool with no schema-level documentation.

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 clearly states 'Lista pedidos' (lists orders), specifies the exact endpoint GET /v2/pedidos, and is distinct from sibling tools like mercos_create_pedido and mercos_update_pedido. The verb+resource combination is specific and immediately identifies the tool's function.

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?

It gives clear, actionable usage guidance: 'Use alterado_apos pra incremental' tells the agent how to perform incremental listing. It does not explicitly discuss exclusions or named alternatives, but the context of listing orders is clear enough for ordinary use.

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