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

Adds real context beyond the readOnly/idempotent/openWorld annotations: pricing methodology (on-chain Uniswap v3 pools on Base), the pricing gap (tokens left unpriced), the cost model (0.005 USDC per call) and latency (5000 ms p95). These are exactly the kind of operational details annotations cannot convey.

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?

Information-dense and front-loaded: the when-to-use clause and exclusions come first, followed by return/cost/latency details in a single compact block. The trailing 'Category: Trading' is filler that does not earn its place.

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?

Even though an output schema exists, the description usefully signals cost, per-call latency, supported chains, pricing source and the unpriced-token caveat. What remains thin is sibling differentiation against wallet_portfolio/wallet_balances, the main thing an agent still needs to decide.

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 description coverage is 100%, so the schema already documents address, chains and response_format. The description reinforces chain coverage (Ethereum and Base) and the 0x address shape but adds little parameter meaning 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 verb and resource ('wallet portfolio value in USD', 'net worth', 'token balances with USD value'), which is more concrete than the title. However, it never distinguishes itself from the very close siblings blackwood_wallet_portfolio and blackwood_wallet_balances, leaving the agent to infer which of the three to pick.

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 an explicit 'use when' clause and a concrete 'do not use for' list (solana wallets, transaction history, NFTs, DeFi positions, long-tail tokens), which is strong boundary-setting. It stops short of a 5 because it never names the alternative sibling tools an agent should route to for those excluded cases or for the overlapping portfolio/balances cases.

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