defi-portfolio

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

No annotations provided, so description carries full burden. Mentions cost ($0.010/call) but not read-only nature, authentication needs, rate limits, or data freshness. Cryptic phrase about '41 payers' adds confusion.

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?

Concise three sentences with front-loaded purpose. The last sentence about '41 payers' is obscure and unnecessary for tool selection, slightly reducing clarity.

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?

No output schema, so description should cover output format and behavior. Does not describe return structure (per token vs. aggregate), error handling, or supported chains beyond names. Lacks completeness for an agent to fully understand tool behavior.

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 baseline is 3. Description adds no new meaning beyond schema; repeats chain info already in parameter descriptions.

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 is a multi-chain DeFi portfolio scanner that returns token holdings and USD values for EVM wallets across four chains. Distinguishes from wallet-balance and other siblings by specifying token coverage and multi-chain scope.

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?

Implies usage through description: use for multi-chain DeFi portfolio scanning. However, no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives among siblings.

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