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

Annotations already declare readOnlyHint=true and openWorldHint=true, so "Read-only" largely repeats what is structured. The one useful addition is the scope note that both spot and futures orders are covered, though pagination, rate limits, and what happens without an active connection are unstated.

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 short sentences with the resource and scope front-loaded and the safety note trailing. Nothing is wasted, though the read-only clause could be dropped as redundant against the annotations.

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 simple three-parameter read tool with full schema coverage and safety annotations, the description covers purpose and scope adequately. No output schema exists, so return shape is unexplained, but that is a minor gap for a list query.

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 each parameter already has an example and a precedence rule for connectionId, so the description adds no parameter meaning. Baseline 3 is appropriate.

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?

"List open orders on a CEX connection (spot + futures)" gives a specific verb, resource, and scope, so an agent can tell it retrieves open orders rather than fills or positions. It stops short of explicitly separating itself from a sibling such as list_fills, which are the closest thing to a differentiator in the catalog.

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 read-only framing implies this is a safe query tool, but there is no explicit statement about when to use it rather than list_fills or another read tool, and no prerequisites noted. The only hint is in the schema, where connectionId is said to take precedence over exchange.

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