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

With no annotations, the description carries the behavioral burden and does disclose data provenance (N-MFP3, N-PORT, 10-K), granularity (month by month), and specific metrics such as Rule 2a-7 liquidity, $1 price held, 7-day yield, months without a loss, worst month, compounded return, and dividend years/yield. It does not cover read-only status, rate limits, or pagination, but it adds substantial context beyond the schema.

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 information-dense but opens with a metaphor ('Kept its word') that delays the plain purpose, and 'boat signs' is unclear. The remaining sentences efficiently enumerate vehicle types and data points, but the structure could front-load the core retrieval action.

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 read-only, one-parameter tool with no output schema, the description adequately explains what data categories are returned and from which filings. It lacks detail on return format or pagination, but the metric-level enumeration compensates for the missing output schema.

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% and the single ticker parameter is already documented with an example and the empty-for-all behavior. The description repeats the ticker/no-ticker distinction ('for one record, or none for all') without adding format or filtering semantics beyond the 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?

The description identifies a specific subject: whether cash-sweep vehicles (money-market funds, short-term Treasury/bond funds, dividend payers) 'kept their word' month by month from SEC filings. It names the filing types and metrics for each, so an agent can tell this is a data-retrieval tool about sweep vehicles, though it does not explicitly contrast with siblings.

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 only says 'Give a ticker for one record, or none for all,' which mirrors the schema and is about parameter use, not when to choose this tool over alternatives. There is no when/when-not guidance or pointer to siblings like get_etf_health or get_cash_leaders.

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