Get Stock Token portfolio

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, and the description reinforces 'Read-only.' It adds useful behavioral context beyond annotations by specifying the exact output components (token balance, share-equivalent, USD value, USDG cash balance) and the 'Multiplier-correct' aspect, which is not derivable from structured fields.

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?

A single sentence front-loads the core purpose and then efficiently lists the portfolio components. Every word earns its place; no filler or repetition beyond the useful 'Read-only' safety confirmation.

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 simple one-parameter, read-only tool with no output schema, the description adequately covers what the agent will receive: per-position balance, share-equivalent, USD value, and cash balance. It does not mention empty-address behavior or error cases, but these are minor gaps for this context.

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%, with the address parameter clearly described as 'Wallet address (0x…40 hex) to value.' The description adds no new parameter format or syntax, only rephrases 'any address,' which is redundant with the schema.

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?

Description uses a specific verb ('Get') and resource ('Stock Token portfolio'), and details exactly what is included: per-position token balance, ERC-8056 share-equivalent, USD value, and USDG cash balance. It distinguishes itself from siblings like get_stock_quote and list_stock_tokens by focusing on a full address portfolio.

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 provides clear context: 'for any address' and a list of returned components, making it obvious when to use this tool for wallet portfolio holdings. It does not explicitly name alternatives or exclusions, so it stops short of a 5.

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