getFundDisclosureDates

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

Description adds no behavioral info beyond annotations. Annotations already indicate read-only and idempotent, but the description does not address pagination, rate limits, or data freshness.

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?

Two sentences, efficient but second sentence is generic fluff. Could be slightly tighter.

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 no output schema and many sibling tools for filings and disclosures, the description fails to clarify the specific role of this tool. Incomplete for the complexity.

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% but the description mentions 'filing dates' which are not reflected in parameters. Creates confusion; does not compensate for the mismatch.

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 states it retrieves detailed disclosures for mutual funds and ETFs based on filing dates, but lacks specificity on how dates are used or returned. Does not differentiate from sibling tools like getFundDisclosure or getForm13FFilingDates.

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 alternatives. No exclusions or context for appropriate usage.

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