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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description confirms 'Read-only' rather than contradicting it. It adds real context beyond the annotations: the tool fetches holdings itself, paper and live accounts are kept separate, and it always returns a text summary plus a botspot.trade link even where the interactive panel isn't supported.

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 routing instruction and the answer shape are front-loaded, and nearly every sentence carries decision-relevant information. It runs long for a single tool and the interactive-panel/link sentence, while useful, could be tightened.

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?

There is no output schema, but the description describes the return payload in concrete terms (per-account table fields, allocation donut conditionality, text summary plus link). Combined with the explicit routing rule, an agent has everything needed to call it correctly without a prior discovery step.

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 0%, so the description must carry the parameters. It explains the sort dimension ('Sort by value or pnl') and partially implies the mode semantics ('Paper and live accounts remain separate', 'across connected accounts'), but never enumerates live/paper/all and says nothing about brokerCredentialId. Useful but incomplete compensation for the coverage gap.

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+resource and specifies exactly what the answer looks like (holdings table per account with value, unrealized P&L in dollars and percent, weight, plus an allocation donut when totals are complete). It explicitly distinguishes itself from the sibling fetchers get_broker_positions and get_broker_account_snapshot.

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?

Gives an unambiguous routing rule: 'use this first for a general holdings or allocation question across connected accounts, without prefetching get_broker_positions or get_broker_account_snapshot.' That names the alternatives and the condition that selects them, plus a clear negative instruction against prefetching.

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