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

Annotations declare readOnlyHint=true, and the description is consistent ('this read-only connector cannot perform'), adding real value beyond the annotation: the regulatory rationale, the browser fallback note, and the fact that the response is a precise link. It stops short of describing exact return format, though that is minor for a link tool.

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 core behavior and the when-to-use condition; the single long sentence carries some redundancy between the parenthetical list and the following clause, but every element is relevant and nothing is wasted.

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 one-parameter, no-output-schema tool whose only job is to emit a link, the description covers purpose, trigger conditions, and the link's usage note. Return-format detail is unnecessary here, so the definition is essentially 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?

Schema coverage is 100% and the schema already gives examples for 'action', so baseline is 3; the description goes further by enumerating the action categories (trades, holdings, watchlists, alert subscriptions, advice) that map onto that single parameter, genuinely enriching its semantics.

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 ('return the exact Returnolio app link') and immediately scopes it to actions the read-only connector cannot perform, which cleanly distinguishes it from all data-retrieval siblings like get_top10, my_portfolio, and compare_stocks.

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 says when to use it ('whenever the user wants to DO something the connector cannot do') and enumerates the triggering categories (trades, holdings/watchlist changes, alert subscriptions, personalized advice), so the agent can route without inference.

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