historico_envio

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

No annotations are provided, so the description is the sole behavioral source. The verb 'Obtém' implies a read-only operation, but additional context such as ordering of history, error conditions, or access requirements is not disclosed. It does not contradict annotations (none exist), but adds minimal transparency beyond the core action.

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 a single, concise sentence in Portuguese with no superfluous words. It is appropriately sized for the tool's simplicity and front-loads the main action efficiently.

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?

The tool has one parameter and no output schema. The description states the action but does not describe the expected return structure (e.g., array of statuses, timestamps) or ordering. This leaves gaps for an agent, but for a simple history retrieval it is minimally adequate.

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 fully covers the single parameter 'shipment_id' with a clear description ('ID do envio'). With 100% schema coverage, the baseline of 3 applies, and the tool description adds no extra parameter semantics but does not need to.

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 uses a specific verb ('Obtém' - gets) and a specific resource ('histórico de status de um envio' - status history of a shipment). It clearly distinguishes from the sibling tool 'detalhes_envio', which likely provides current details rather than historical statuses.

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 no guidance on when to use this tool versus siblings like 'detalhes_envio' or 'listar_vendas'. There are no preconditions, alternative conditions, or exclusions mentioned, leaving the agent without context for tool selection.

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