order_execute

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

Without annotations, the description discloses 'fast', 'preview-based', and 'no automatic retry'. However, it omits side effects, error states, and success behavior. The disclosure is partial.

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?

Two concise sentences with no wasted words. Could be improved with clearer structure (e.g., bullet points for requirements), but overall efficient.

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?

With 4 parameters, no output schema, no annotations, and many sibling tools, the description is too brief. It fails to explain the execution flow, return values, or how to obtain previewId/requestHash, leaving the agent underinformed.

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 coverage is 0%, so description must explain parameters. It only implicitly mentions previewId and requestHash in the requirement list, but does not clarify confirmation format or delegatedAuthority object. Meaning is lacking.

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 it's for preview-based order execution, with a specific verb ('execute') and resource ('order'). It implies a link to order_preview, but does not explicitly differentiate from sibling order_create.

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?

Lists prerequisites (previewId, requestHash, confirmation, gates) but does not specify when to use vs alternatives like order_create or order_validate, nor when not to use.

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