account_portfolio

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

Discloses important behavioral traits: Data API values lag the matching engine and are not exchange reconciliation truth. This adds transparency beyond the input schema. No annotations provided, so description carries full burden.

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 dense sentences, no wasted words. Front-loaded with core purpose, efficient in structure.

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?

Covers modes, wallet configuration, and data lag caveat. Output schema exists, so return values are documented elsewhere. Limit parameter omission is a gap, but overall sufficient for an agent given the output schema.

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?

Only the wallet parameter is partially explained (public wallet address for live mode). The limit parameter is not mentioned in the description; schema has 0% coverage, so the description fails to explain its purpose.

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 the current portfolio without placing an order, distinguishing it from order placement tools. However, it does not explicitly differentiate from sibling tools like account_collateral, though 'portfolio' implies a broader view.

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?

Provides clear guidance on when to use paper mode vs. live mode, and how to configure wallet address via parameter or environment variable. Lacks explicit when-not-to-use or comparison to siblings.

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