List strategies deployed on an account

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the read-only nature is known. The description adds useful context about the returned data (symbol, timeframe, status) and the accountId caveat. No contradictions; missing only minor details like error behavior or pagination, which are less critical given the output schema exists.

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 delivering distinct value: purpose, accountId clarification, and alternative tool reference. No fluff or repetition, well front-loaded with the core function.

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 list tool, rich annotations, existing output schema, and exact parameter guidance, the description is fully complete. It covers purpose, usage, parameter caveats, and alternatives without needing to explain return values since an output schema is present.

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 100% and the schema already documents accountId as the id field from list_accounts, not the MT5 login. The description reiterates this same information, adding no new meaning beyond the schema; thus 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?

The description clearly states the tool lists strategies (expert advisors) deployed on one MT5 account, including symbol, timeframe, and status. It distinguishes this from the platform-wide catalog via the explicit reference to list_strategies, making sibling differentiation clear.

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 provides explicit guidance on when to use this tool versus list_strategies, and clarifies the exact accountId format with a warning against using login. This gives the agent clear context and exclusion criteria for tool selection.

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