Get Account Summary

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

The readOnlyHint annotation already signals a safe read operation, but the description adds behavioral context: it is 'curated' and returns a subset of fields. This goes beyond the annotation by explaining the tool's scope and what fields to expect, though it doesn't describe error handling or authentication requirements.

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 long, front-loads the core purpose, and immediately provides the actionable alternative. Every word earns its place, and the field list is compact yet informative.

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?

With one optional parameter, full schema coverage, and a readOnlyHint, the description covers the essential context: what the tool does, what fields it returns, and how it differs from its sibling. The absence of an output schema is mitigated by the field list, though a note about response format would be a minor enhancement.

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% — the single parameter accountId is documented as 'Account ID. Uses default account if omitted.' The description doesn't need to elaborate further, as the schema fully explains the parameter's meaning and optionality.

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 starts with 'Get curated account summary' and enumerates the specific fields (net liquidation, cash, buying power, margin, gross position value, P&L, cash breakdown by currency). It explicitly distinguishes from get_account_summary_full by stating it returns 'the most important fields only,' which prevents confusion among sibling tools.

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?

It provides clear guidance on when to use this tool versus the full version: 'Returns the most important fields only — use get_account_summary_full for all 70+ fields.' This directly addresses the alternative and implies the tool is for quick, curated summaries rather than exhaustive data.

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