Get eToro closed trades

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior. The description adds useful operation-specific context: it is limited to the demo account, returns closed trades with open/close rates, net profit and fees, and is paginated. It still does not explain pagination behavior or authentication needs.

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 no wasted words. The core purpose, scope, return fields, and pagination caveat are front-loaded and easy to parse.

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 listing tool with no output schema and rich safety annotations, the description covers the key facts an agent needs: demo-account scope, closed trades only, date filtering, returned fields, and pagination. It remains incomplete on pagination details and lacks sibling routing, but overall it is sufficient for correct invocation.

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 low at 33%, with only minDate documented. The description adds some semantic value: 'since a date' clarifies minDate as a start date, and 'Paginated' signals that page/pageSize exist and matter. However, it does not explain page or pageSize behavior, defaults, or limits, so the two undocumented parameters remain underspecified.

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 specific verb+resource ('Get eToro closed trades'), scope ('demo account since a date'), and returned fields. It distinguishes closed trades from generic portfolio/PnL siblings implicitly through 'closed trades' and 'open/close rates, net profit and fees', but does not explicitly say how it differs from tools like etoro_get_pnl.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative sibling is named. The description only implies usage by specifying 'closed trades of the demo account since a date', leaving the agent to infer context.

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