Restart Grid Order

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

Annotations already indicate readOnlyHint=false (mutation), idempotentHint=true (safe to retry), and destructiveHint=false (non-destructive). The description adds the context that the order must be suspended, which is a useful constraint, but does not describe what happens on success or any side effects beyond resuming. With annotations covering the safety profile, this is adequate but 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 sentence with no filler: 'Restart (resume) a suspended grid order by order_id.' It front-loads the action and states the prerequisite, making it highly concise and clear.

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 simplicity (one parameter, no output schema) and the annotations covering behavior, the description is complete enough. It could be improved by explaining what happens on success (e.g., the order resumes trading) or error conditions, but for a basic resume action, it's sufficient.

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% and the schema already explains order_id as 'Grid order ID.' The description adds no additional meaning or format guidance beyond that, so it falls at the baseline of 3 since the schema does the heavy lifting.

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 the action: restart (resume) a suspended grid order, specifying the target resource (grid order) and the condition (suspended). This distinguishes it from siblings like grid_suspend and grid_cancel by explicitly naming the resume effect.

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 implies the appropriate use case: when a grid order is suspended. It says 'Restart (resume) a suspended grid order,' which tells the agent it should only be used on suspended orders. However, it does not explicitly mention when not to use it (e.g., for active or cancelled orders) or contrast with alternatives like grid_replace, so it's clear but not exhaustive.

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