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

With no annotations, the description carries the full burden. It usefully discloses that NFT holdings are excluded from portfolio totals because there is no reliable price, which is real cross-tool context, but it says nothing about read-only nature, wallet scope, or result limits.

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?

Two short sentences with no filler, front-loading what the tool returns before the pricing caveat. Efficient, though the terse phrasing reads more like a fragment than a complete statement.

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 one-parameter list tool with no output schema and no annotations, the description covers what is returned and the pricing caveat. It omits whether wallets are auto-discovered, whether results are paginated, and whether the call is a safe read, leaving moderate gaps.

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 the chain enum and its default are already documented. The phrase 'on one network' still adds meaning by telling the agent that only a single chain can be queried per call, which the schema does not state.

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?

Names the resource (NFTs) and constrains scope precisely: the user's EVM wallets on a single network. No explicit verb, but the retrieval intent is unambiguous and the resource is distinctive enough to separate it from siblings like get_asset or get_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?

Gives no when-to-use guidance, no alternatives, and no prerequisites. The only adjacent hint is that NFTs are excluded from the portfolio total, which implicitly routes the agent here after a portfolio call, but that must be inferred.

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