Get raw eToro PnL/positions payload

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It adds useful context by stating the tool is read-only and produces large output, which helps set expectations. However, it does not mention authentication requirements, rate limits, potential errors, or the exact response format, leaving some behavioral gaps.

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?

The description is a single, front-loaded sentence that immediately names the endpoint and then lists the payload contents. Every word earns its place, with no redundancy or filler. This is exemplary conciseness.

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 tool has no parameters and no output schema, the description provides adequate context by specifying the exact endpoint, the types of data included (open positions, pending orders, account-level PnL), and cautioning about large output. It does not detail pagination or interpretation, but for a simple raw dump tool, the description is sufficiently complete.

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 has zero parameters, and per the rubric the baseline is 4. There is no parameter detail needed, and the description correctly focuses on the return value rather than inputs. It does not introduce any parameter confusion.

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 uses a specific verb ('Returns') and explicit resource ('/trading/info/real/pnl') with a clear scope: every open position, pending order, and account-level PnL. This differentiates it from siblings like etoro_portfolio_summary or etoro_holdings, which likely provide processed/summary data rather than the raw payload.

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 implies usage by emphasizing 'raw response' and 'large output', suggesting it is for consumers needing unprocessed data rather than summaries. However, it does not explicitly state when to choose this over sibling tools or mention any exclusion criteria, so the guidance remains implied rather than direct.

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