dzengi_list_open_orders

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds the 'currently open' state scope and the 'normalized symbol' behavior, but does not disclose output format, ordering, or pagination.

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?

A single sentence with no filler. The core action and the optional parameter behavior are both front-loaded and immediately usable.

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 read-only list operation with one optional parameter)Skip enriched by readOnly and openWorld annotations, the description is adequate for selection and invocation. It does not describe the return payload, but that is a minor gap for this 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 coverage is 0% and only provides type and maxLength for symbol. The description adds valuable meaning: the symbol parameter is optional and will be normalized, which is essential information the agent would otherwise lack.

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?

Description uses a specific verb ('read'), a clear resource ('currently open orders'), and a precise qualifier ('optionally filtered by a normalized symbol'). It distinguishes the operation from general order fetching.

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 phrase 'currently open orders' gives clear context and implicitly excludes historical, cancelled, or filled ordersholistically. It does not name sibling tools like dzengi_list_positions or dzengi_get_order, but the context is sufficient for typical selection.

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