get_holdings

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

Discloses that cost_basis may be unavailable for cash-equivalent positions, adding value beyond the readOnlyHint annotation. No contradictions with annotations.

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?

Concise two-sentence description plus a note, front-loaded with main action and no unnecessary detail.

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 key aspects: returned data, filters, optional history, caveat about cost basis. Pagination is implied by limit/offset in schema. No output schema, but description compensates.

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 coverage is 100%, so description adds marginal value by explaining return fields and joins, and noting default false for include_history. Parameters are well-documented in schema.

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?

Description clearly states 'Get current investment holdings with position-level detail' and lists specific fields returned (ticker, name, quantity, etc.), distinguishing it from siblings like get_accounts and get_balance_history.

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?

Mentions filtering by account or ticker and optional history inclusion, providing clear context for when to use this tool. Does not explicitly state when not to use, but purpose is distinct from siblings.

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