Lister les comptes Quantower

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

Annotations declare readOnlyHint=true, so safety is covered. The description adds value beyond that by enumerating the return fields (accountId, connectionId, balance, devise, PnL) in the absence of an output schema, plus the demo-only operating constraint. It omits any note on pagination or behavior when no accounts exist.

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 compact sentences that front-load the purpose, then filter, then constraint. No filler, though the parenthetical field list and the filter sentence partially duplicate information the schema already carries.

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 single-parameter read tool with no output schema, the description covers purpose, return fields, filtering, and the safety constraint. Only minor gaps remain, such as pagination or empty-result behavior.

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 single connectionId parameter is already documented with a pointer to quantower_list_connections. The description's "Filtrable par connectionId" merely restates the schema, adding no syntax or format detail. Baseline 3 is correct.

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?

States a specific verb and resource ("Liste les comptes Quantower") and enumerates the returned fields, so an agent knows exactly what it gets back. It is broadly distinguishable from siblings like quantower_get_positions or quantower_list_connections, though it never explicitly says what it is not.

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 a clear usage constraint: use only with demo accounts during development. That is an explicit when-to-use boundary. It stops short of naming an alternative tool or explaining what to do for live accounts, so it is not a full 5.

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