Get portfolio + P&L

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

Annotations already declare readOnlyHint=true, so safety is clear. Description adds useful behavioral context by detailing the data returned (credit, positions, P&L, exposure) and noting demo/real mode compliance.

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?

Single, well-structured sentence. Purpose is front-loaded: 'Get the current account's portfolio with P&L'. Every part adds value without redundancy.

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 parameterless read-only tool with no output schema, the description completely covers what the tool does and its behavior (respects demo/real mode). No gaps.

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?

Input schema has no parameters (0 params). Description does not need to explain parameters; baseline for 0 params is 4. It clearly states what the tool returns without parameter details.

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?

Description explicitly states it retrieves the current account's portfolio with P&L, listing specific data items (credit, open positions, unrealized P&L, etc.). It differentiates from sibling tools like etoro_get_user_portfolio by specifying 'current account'.

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?

Description indicates what the tool does but lacks guidance on when to use vs alternatives. It mentions respecting demo/real mode, but no exclusions or comparisons to other tools are provided.

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