List eToro watchlists

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds some value by stating that items are returned as instrument ids, but it does not explain pagination behavior, whether built-in watchlists are included, or other operational details.

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 noun phrase rather than a structured sentence, so it is terse but under-specified. It is not front-loaded with a clear verb or usage context, leaving important information absent.

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 two undocumented parameters, no output schema, and no usage guidance, the description is too thin for an agent to call the tool confidently. It states the broad return content but omits parameter meanings, pagination, and the role of built-in watchlists.

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 0% for both itemsPerPage and includeBuiltin, and the description does not mention either parameter. The definition gives an agent no way to understand the two inputs beyond their bare names and defaults.

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 names the specific resource (the user's watchlists) and what each contains (items / instrument ids), so an agent can tell it is a read/list tool for watchlists. It lacks an explicit verb, but the title supplies 'List' and no sibling tool covers watchlists, making the purpose clear.

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 guidance on when to call this tool, when to avoid it, or how it relates to the portfolio and instrument siblings. The agent must infer its usage from the name alone.

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