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

With no annotations, the description carries full burden. It transparently describes the operation: 'derives the bound account on-chain and lists + prices its holdings.' However, it doesn't explicitly state read-only nature or edge cases like non-ERC-6551 NFTs, minor gaps for a valuation tool.

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?

Three sentences with the core purpose front-loaded in the first sentence, followed by context and usage. Each sentence adds value, but the ALL-CAPS emphasis and the aside 'which nobody else surfaces' make it slightly longer than necessary.

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 complex tool with no output schema, the description covers what it does, why it's unique, and when to use it, including the on-chain derivation mechanism. It lacks explicit return-format or total-value statement, but 'lists + prices its holdings' reasonably implies the output.

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%, so baseline is 3. The description adds meaning by explaining that collection is the NFT collection address and token_id identifies the NFT, and it clarifies the chain context (Robinhood) which informs the default chain parameter. This adds process insight beyond 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?

Clearly states it values the assets held inside a Robinhood-chain NFT (ERC-6551 token-bound account), using a specific verb and resource. The description distinguishes it from siblings by noting 'which nobody else surfaces' and provides concrete intended uses.

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?

Provides explicit use-case scenarios in quotes: 'what's inside this Robinhood NFT / what is this broker worth / does this NFT hold stock tokens.' While it doesn't list alternatives or exclusions, the differentiation from floor-price tools is implied through 'floor PLUS its contents -- which nobody else surfaces.'

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