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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description restates 'Read-only' but also adds real value: it notes delta is only used when the broker reports it, that an interactive panel appears in MCP Apps, and that a text summary plus botspot.trade link are always returned. It does not mention auth/credential requirements, which is the main remaining gap.

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 two motivating user questions, then the returned data, then channel behavior. Dense but every clause carries information; the quoted questions could be trimmed but they aid recognition.

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, the description properly enumerates the returned values and the two delivery channels (interactive panel vs. text+link), which is what an agent needs. Missing only guidance on the brokerCredentialId parameter, which is a real but narrow gap.

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 2 parameters, so the description must compensate. It implies symbol accepts a stock ticker or an options underlying and can be an option position, but says nothing about the brokerCredentialId parameter or how/when to supply it, leaving half the parameters undocumented.

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 a specific verb (show) and a specific resource (one position), and spells out the exact fields returned (value, unrealized P&L, shares, average cost, delta-based exposure, payoff chart). It doesn't distinguish itself from close siblings like show_holdings or get_broker_positions, so it stays at 4.

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?

The quoted user questions ('How is my TSLA position doing?') imply when to reach for this tool for a single symbol, but there are no explicit conditions/exclusions and no named alternatives among the many sibling position/holdings tools. Usage is inferred rather than stated.

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