get_portfolio_summary

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

With no annotations provided, the description carries the behavioral disclosure burden. It openly describes the operation as a read-oriented 'overview' and 'snapshot', and lists the data categories returned. It does not mention response format or potential latency, but the aggregate, non-mutating nature is clearly conveyed.

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 two sentences with no filler. The core value proposition and scope are front-loaded, and the benefit over multiple API calls is stated in one concise clause. Every sentence contributes to tool understanding.

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?

For a single-parameter read-only summary tool, the description is largely complete: it names the scope and the major content categories. There is no output schema, so the description partially compensates by listing what the snapshot includes, though it could specify field-level details or ordering behavior for full completeness.

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?

The schema covers the only parameter (currency) with an enum and a 'Currency' description, so schema coverage is 100%. The description adds no further parameter-specific detail, such as how the currency affects which positions or orders are included, but the schema already provides sufficient semantics.

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 states a specific verb and resource: a one-shot account overview for a currency. It enumerates the contents (balances, margin usage, equity, positions with P&L, open orders), which clearly distinguishes it from narrower siblings like get_account_summary, get_positions, and get_open_orders.

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?

The description clearly implies when to use this tool: when a broad account snapshot is needed without making multiple separate API calls. It does not explicitly name excluded alternatives or edge cases, but the phrase 'Saves multiple API calls into a single comprehensive snapshot' provides actionable context for tool selection.

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