portfolio_get_valuation

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

Discloses aggregation scope, fiat conversion, return breakdown, and dust filtering. Notes caching via force_refresh parameter. No annotations provided, so description carries full burden; could mention authentication or rate limits.

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?

Three sentences, front-loaded with purpose, no redundancy. Efficiently conveys key features.

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?

Describes return values (total, breakdown, individual) and mentions dust filtering. No output schema, so description compensates well. Could note data volume or performance implications.

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 has 100% coverage with descriptions for all 3 parameters. Description adds minor value: default EUR and caching behavior. No parameter details beyond schema, so baseline 3 is appropriate.

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 calculates total portfolio value by aggregating across Wallet, Pro Trading, Earn/Staking, and Loans. Distinguishes from sibling tools which are section-specific (e.g., broker_get_*, pro_get_*, earn_get_*).

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?

Implicitly indicates usage for overall portfolio view, but no explicit guidance on when to use versus alternatives or when not to use. Lacks mention of prerequisites or context.

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