Create Order

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description simply states 'creates order', which aligns. However, it adds no additional behavioral context such as side effects, webhook behavior, authorization needs, or rate limits. The only added detail is the endpoint, which is minimal.

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 that front-loads the core action. It is appropriately sized and contains no filler, earning its place with the essential information.

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 the tool's complexity (14 parameters, nested objects, no output schema) and minimal description, the agent is left without critical context about parameter behavior, return values, or side effects. This is completely inadequate for making correct invocations.

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 has 14 parameters with 0% description coverage, so the description must compensate. It only mentions 'itens' (items) and 'pagamento' (payment), which loosely map to 'items' and 'method', but does not explain the other 12 parameters like customerId, couponCode, shippingAddress, or metadata. This leaves most parameters ambiguous.

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 a specific verb ('Cria') and resource ('pedido'), and provides the endpoint ('/v1/orders'). It distinguishes from siblings like create_transaction and create_cashout by focusing on orders, though it does not explicitly compare with them.

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 gives no guidance on when to use this tool versus alternatives such as create_transaction or list_orders. There is no mention of prerequisites, exclusions, or preferred scenarios, leaving the agent to infer usage solely from the tool name.

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