schwab_get_total_dividends

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

Discloses the 60-day default lookback and how to override it. This is useful behavioral context. However, no annotation exists, and the description does not explicitly state read-only or destructive nature.

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 action, then parameter details. Every sentence adds value. Arg list is efficient.

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 purpose, parameters, and a key behavioral constraint. With an output schema present, not needing to explain return values. Minor lack of explicit use-case differentiation from siblings.

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?

Adds significant meaning beyond the schema: explains account_hash source, date format, and the 60-day lookback constraint. Schema coverage was 0%, so description fully compensates.

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 clearly states the tool gets 'aggregate dividend totals with year grouping'. This is specific and distinguishes it from sibling tools like 'schwab_get_dividends' which likely return individual dividends.

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 on when to use this tool vs other dividend-related siblings. Does not mention alternatives or when not to use. Only provides one minor caveat about start_date.

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