vendas_para_enviar

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

With no annotations, the description carries the full burden. It discloses that it checks the status of each shipment and only returns those with 'ready_to_ship', and that it filters for paid sales. This is behavior beyond the schema, showing the internal logic. It does not mention side effects (none implied) or return format, but the behavior is clearly described.

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 two sentences long, front-loaded with the main purpose, then a behavioral detail about status checking. Every sentence adds value, and there is no unnecessary verbosity.

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 simple listing tool with no output schema, the description adequately covers what is returned (paid, unshipped, ready-to-ship sales) and the optional filter. It is missing explicit mention of ordering or pagination, but these are not critical for this type of operation.

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 input schema already provides full descriptions for both parameters (limit and apenas_hoje), so the baseline is 3. The description's mention of optional filtering by today's deadline repeats schema information without adding new semantics.

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 the tool lists paid sales that are not yet shipped and are 'ready_to_ship', with an optional filter for today's deadline. This specific verb+resource+scope distinguishes it from siblings like listar_vendas (likely all sales) and detalhes_envio (individual shipment info).

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 provides a clear context for use (identifying orders ready for dispatch) and mentions an optional filter for today's deadline, which implies when this tool is appropriate. It does not explicitly mention when not to use it or point to alternatives, but the sibling context is available.

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