Pedidos por data (e-commerce)

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals the core selection behavior (orders changed after a date) but does not mention whether the result is a list, count, or detailed records, nor any pagination or ordering behavior. Some transparency is present, but significant gaps remain.

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 compact sentence with no filler or redundant information. It is front-loaded with the resource and condition, though it reads more like a fragment than a full instruction.

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 tool with no output schema and no annotations, the description should explain what the caller receives and any relevant usage context. It only provides the input format and a vague filter, leaving the return value and invocation context to inference.

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 schema only defines 'data' as a string with no description, so the tool description's mention of 'dd/MM/yyyy' adds crucial format context. However, it does not clarify whether the date is inclusive, what timezone applies, or whether the date refers to modification date specifically, leaving some ambiguity.

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 identifies a specific resource ('Pedidos/pré-vendas') and a clear criterion ('alterados após dd/MM/yyyy'), so an agent can tell this is a query for orders modified after a given date. It does not explicitly name a sibling alternative, but the date-based scope is reasonably distinct from the other order-related 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 states what the tool does but gives no guidance on when to choose it over alternatives like pedidos_consultar or pedido_status. There are no exclusions, prerequisites, or context about the intended use case.

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