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

With no annotations provided, the description carries the burden of behavioral disclosure and does well: it indicates a read-only portfolio snapshot, mentions spam/unpriced filtering, names Blockscout as the live data source, and lists the output fields. It does not discuss rate limits, error behavior, or the payment mechanics behind the $0.01 x402 mention, but the core behavior is clearly disclosed.

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?

The description is compact and front-loaded with the core value and pricing, followed by output fields, use cases, chains, and data source. It is a bit dense with marketing phrasing, but each clause adds useful information and nothing is redundant.

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?

Because there is no output schema, the description appropriately enumerates the return content: holdings, prices, values, percentages, total value, concentration, and filtering. It also covers supported chains and data source. The only notable gap is the undocumented x_payment parameter, which an agent would need clarified to invoke the tool correctly.

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 67%: wallet and chain are documented, but x_payment has no schema description. The description adds useful semantics for chain by enumerating supported values and implies wallet's role, but it does not clarify what x_payment is or how to supply it, so it does not fully compensate for the gap.

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?

The description clearly states the tool returns any wallet's token portfolio with a specific list of computed fields: amount, live USD price, value, portfolio percentage, total value, and concentration. It also names the use case ("bagcheck") and supported chains, making it easy to distinguish from sibling tools like smart_money_wallet_activity or get_chain_erc20_balance.

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 explicitly positions the tool for copy-trading, whale-watching, risk, and research agents, giving strong context on when to invoke it. It does not explicitly name alternative tools or state when not to use this tool, so it falls short of full directional guidance.

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