schwab_get_dividends

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

No annotations are provided, so the description carries the full burden. It only states the basic purpose (get dividends) without disclosing potential pagination, data freshness, error handling, or that it is a read operation. The output schema exists but is not described in the text.

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 concise: one sentence plus an argument list. It is front-loaded with purpose. The 'Args:' block is slightly redundant given the schema but still efficient. No unnecessary words.

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 simple list tool with 3 parameters (1 required) and an output schema, the description covers the essential purpose and parameter meaning. It lacks details on constraints (e.g., date range validation) but is adequate for the complexity level.

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 0%, so the description compensates. It explains 'account_hash: Account hash from schwab_account_numbers' and specifies date format 'YYYY-MM-DD' for optional start/end dates. This adds meaning beyond the bare property names.

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 'Get dividend payments for a Schwab account.' It clearly identifies the verb and resource. The parameter list implies filtering by account and optional date range, but does not explicitly differentiate from sibling tools like schwa_get_dividends_by_symbol or 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 alternative dividend tools. The description does not specify prerequisites (e.g., call schwab_account_numbers first) or mention that it retrieves per-account dividends, not per-symbol dividends.

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