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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds genuinely new context — 'Free.' (no payment/x402 cost) and the fact that results are per-vault with shares and current USD value — which is not derivable from the annotations.

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 with no filler and an explicit list of return contents. Slightly awkward that 'Free.' leads ahead of the actual purpose, but nothing is wasted.

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?

An output schema exists and annotations are rich, so return values and safety need no repetition. The description supplies the one non-obvious behavioral fact (no cost) plus scope. Only the lack of any when-to-use guidance keeps it short of complete.

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?

Only one parameter (address) with 100% schema description coverage, so the schema already carries its meaning. The description's 'an address' adds no format, chain, or validation detail beyond the schema's pattern. 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 retrieval over a specific resource — everything an address owns in the tokenized stock basket — and enumerates the payload (vaults, shares, USD value). That scope cleanly separates it from siblings like stocks_basket (the basket definition) and stocks_vault (a single vault).

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 only usage signal is the cost note 'Free.' There is no statement of when to call this versus stocks_vault or stocks_basket, no prerequisites, and no exclusions. An agent must infer usage from the name alone.

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