List pending orders on an account

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds valuable behavioral context: reads live from the terminal, zero-valued sl/tp/priceStopLimit meaning not set, and ticket being the cancellation handle. This goes beyond annotations without contradicting them.

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?

Three sentences, each earning its place: core purpose, live-read clarification, unfilled-vs-filled distinction and alternative, parameter guidance, and zero-value semantics. No redundant or filler content.

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 simple one-parameter tool, presence of an output schema, and thorough annotations, the description covers all necessary context: purpose, usage, edge cases (zero values), and cross-reference to list_positions. Nothing missing.

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?

The schema covers 100% of parameters and already explains accountId as the id field from list_accounts and not login. The description repeats this guidance, providing no additional meaning beyond the schema. Baseline 3 is appropriate for full schema coverage.

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 tool lists pending limit and stop orders on one MT5 account, with a specific verb ('List') and resource ('pending limit and stop orders'). It distinguishes from related tools by explicitly noting these are unfilled orders, unlike list_positions for open positions.

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?

Provides clear when-to-use context: it explains that the tool reads live pending orders and explicitly offers an alternative, 'use list_positions' for filled positions. Also clarifies the correct accountId parameter and how to interpret ticket for cancellation.

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