Open the eToro action history in the browser

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint/idempotentHint, and the description adds non-obvious operational context the annotations cannot convey: bound to 127.0.0.1 only, secret address expires after an hour, and it returns no history data. No contradiction with idempotentHint=false given the expiring address.

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?

Front-loaded with the action, then constraints, then routing in three efficient sentences with no filler. The parenthetical filter list and CSV mention are slightly dense but still earn their place by telling the agent what the page can do.

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 output schema and no parameters, the description supplies everything needed: what opens, where it runs, how long the link lives, and that no data comes back. An agent has no remaining ambiguity about how or whether to invoke it.

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?

Zero parameters and 100% schema coverage, so there is nothing for the description to disambiguate. The parenthetical list of filter dimensions (text, date, environment, action, status) is contextual color rather than true parameter semantics, so it stays at the baseline rather than exceeding it.

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 verb and resource ('Opens a local page in the user's browser') plus the concrete capabilities of that page (search/filter history, view details, see limits, download CSV). It is clearly distinguishable from the sibling that actually returns history data, which it names explicitly.

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?

Explicitly routes the agent away from this tool for data retrieval: 'It returns nothing from the history: use etoro_get_action_history to read it yourself.' That is a clear when-not condition, though it never states the positive case (user wants an interactive browser UI) beyond the opening clause.

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