get_portfolio_snapshot

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read operation via 'Get' but does not explicitly state read-only safety, permission requirements, rate limits, or any side effects. The description only restates the function without adding contextual behavioral traits.

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 a single, focused sentence with no redundant information. It is concise and front-loaded, effectively communicating the tool's purpose without unnecessary filler.

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?

There is no output schema, so the description should clarify the return format or structure. It does not explain what the snapshot includes (e.g., spot vs. funding balances), how it aggregates data, or how it differs from sibling tools. The description is too terse to be fully self-contained for an agent unfamiliar with the context.

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 the schema already documents all three parameters thoroughly. The description's mention of 'live valuation' adds minimal contextual flavor around valuationQuoteAsset, but it does not materially enhance parameter understanding beyond the schema's provided 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?

The description uses a specific verb 'Get' and resource 'balances and a live valuation snapshot', clearly stating the tool's core function. However, it does not distinguish itself from sibling tools like get_spot_account or get_account_overview, which also retrieve balances, so it lacks sibling differentiation.

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 guidance is provided on when to use this tool versus alternatives. The phrase 'in one call' hints at a convenience advantage, but there is no explicit mention of when it should be preferred over sibling tools or any exclusions.

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