Get stock-token positions

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

With no annotations, the description carries full burden. It reveals return details (raw balance, uiMultiplier, real balance, appreciation %) and the behavior of omitting tokens to scan the registry. It does not mention auth requirements or rate limits, but it is clear it is a read operation.

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 just two sentences with no wasted words. The first sentence front-loads purpose and key returns; the second provides a practical usage tip. Every sentence earns its place.

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?

Given no output schema, the description adequately explains the return values and their computation. It covers the key outputs (raw balance, multiplier, real balance, appreciation %). It could specify the structure (e.g., array of objects) but is sufficient for an agent.

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 100%, so baseline is 3. The description adds no extra meaning beyond the schema: 'Omit `tokens` to scan the known-token registry' repeats the schema description. No additional parameter context.

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 clearly states the tool reads wallet positions for Robinhood Chain stock-tokens with a specific verb 'Read' and resource. It distinguishes itself from siblings (rhc_info, quote_swap, execute_swap) by focusing on positions.

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 description implies usage for reading positions but provides no explicit guidance on when to use this tool versus siblings or when to avoid it. It lacks alternative tool mentions or exclusions.

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