arcade_portfolio

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

Discloses that only 'known-token' balances are returned, indicating a specific set of supported tokens. Lacks details on authentication, rate limits, or error conditions. With no annotations, this is adequate but not thorough.

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?

One sentence with no fluff, front-loaded with key action. However, it could include more useful context without being verbose.

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?

Missing critical context: what constitutes a 'known-token', expected output format (e.g., list of balances), error handling, and network specificity. No output schema provided, so description should compensate.

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?

Does not clarify the format of the 'wallet' parameter (e.g., Ethereum address, Solana). Schema has no description coverage, so the description should add context but does not.

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?

Clear verb 'Get' and resource 'known-token balances' with specific scope 'for a wallet address'. Distinct from sibling tools like arcade_swap and arcade_markets.

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?

No explicit when-to-use or alternatives mentioned. Description implies usage for retrieving token balances, but no guidance on distinguishing from other arcade tools like arcade_markets.

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