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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds useful scope context — that ETH is included alongside stock tokens and ETFs, and that values are denominated in dollars — but says nothing about freshness, chain-call failures, or empty-wallet behavior.

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?

One front-loaded sentence with no wasted clauses; the scope ('stock tokens and ETFs') comes first and the extras ('amounts and value in dollars, plus its ETH') follow. Slightly awkward trailing phrase but efficient overall.

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?

A read-only, single-parameter retrieval tool with no output schema; the description adequately covers what is returned (holdings, amounts, dollar values, ETH). Given the simplicity and the annotation coverage, little else is needed, though noting the wallet must be on Robinhood Chain for valid results would close the loop.

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?

With a single parameter at 100% schema coverage, the schema already documents the wallet address and its chain. The description reinforces the Robinhood Chain context but adds no syntax, format, or validation detail beyond the schema, so the baseline 3 applies.

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 resource (stock tokens and ETFs held by a wallet on Robinhood Chain) and what data comes back (amounts, dollar value, ETH). It is clear what the tool returns, but it never differentiates itself from close siblings like portfolio_brief or portfolio_pnl.

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?

There is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as portfolio_brief or portfolio_pnl. The agent must infer usage purely from the noun phrase.

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