Get eToro account PnL

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds two useful pieces of context: that it targets the demo account specifically and exactly which data classes are returned. It stops short of noting any auth, rate-limit, or freshness/valuation caveats.

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 front-loaded sentence with no filler; the subject (unrealized P/L) comes first and the enumeration is compactly parenthesized. Every clause carries information.

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?

With no parameters and no output schema, the description must convey what comes back, and it does enumerate the returned data classes. The remaining gap is the absence of sibling differentiation, which matters given three other portfolio-style tools in the same family.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The parenthetical clarifies what the (parameterless) response covers, which is a reasonable substitute.

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 resource and result: unrealized P/L plus portfolio details, with an explicit enumeration of contents (positions, mirrors, pending orders, orders to open/close). It is clear what the tool returns, but it never distinguishes itself from close siblings like etoro_get_portfolio, etoro_get_portfolio_breakdown, or etoro_get_balances, which an agent must choose between.

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 only scoping signal is 'demo account', which implies a context but is not framed as a when-to-use rule. No alternatives are named and no conditions for choosing this over the other portfolio/balance tools are given, leaving selection to inference.

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