Suspend Grid Order

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

The description adds a meaningful behavioral nuance beyond annotations: it applies to a 'running grid order' and clarifies that the operation is a pause, not a termination. The annotations already provide idempotentHint=true and destructiveHint=false, and there is no contradiction. It could mention side effects or status transitions in more detail, but the combination is sufficient for this simple operation.

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 short, front-loaded sentences. The first states the action and target; the second gives the resume path. Every word earns its place and no unnecessary detail is included.

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 one-parameter mutation with full schema coverage, idempotent/destructive annotations, and a clear sibling relationship to grid_restart, the description is complete. It tells the agent what the tool does, what input it requires, and how to reverse the action. No output schema is present, but none is needed for such a simple suspend 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?

Schema description coverage is 100% for the single parameter order_id, which is documented as 'Grid order ID.' The description merely repeats 'by order_id' without adding format, source, or lifecycle details, so it adds little beyond the schema. A baseline 3 is appropriate because the schema already fully documents the parameter.

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 ('Suspend (pause)') and names the resource ('running grid order by order_id'). It clearly distinguishes this from sibling tools like grid_cancel, grid_restart, and grid_replace by stating the action is a pause, not a cancellation or restart.

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 clearly indicates when to use the tool: to suspend a running grid order. It also explicitly mentions the counterpart, 'Resume with grid_restart,' which helps an agent choose between alternatives. It stops short of listing exclusion cases or conditions like 'do not use if order is already paused,' so it is strong but not exhaustive.

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