Get SEC Filing Calendar

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

Annotations already declare readOnlyHint=true, so the description's mention of 'Get' is consistent. The description adds no further behavioral traits (e.g., rate limits, pagination). It's adequate but doesn't go beyond what annotations provide.

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, front-loaded with the main action, no fluff. Every sentence contributes useful information without repetition.

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?

Given all parameters are optional and well-documented in the schema, and an output schema exists (handling return values), the description sufficiently covers what the tool does. No gaps are apparent for an agent to select and invoke this tool correctly.

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 100%, so the description does not add significant new meaning to parameters. It restates the time window and optional filters in a coherent sentence, which is helpful but not beyond the schema's own descriptions.

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?

Clearly states the verb 'Get' and the specific resource 'forward-looking 10-K / 10-Q SEC filing-deadline calendar'. Distinguishes from sibling calendar tools like get_earnings_calendar by specifying it's for SEC filing deadlines and including optional filters for universe and form types.

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?

The description implies usage for retrieving SEC filing deadlines within a date window and optionally filtering by index universe or form types. While it doesn't explicitly state when not to use or name alternatives, the context of sibling tools (e.g., get_earnings_calendar) provides differentiation.

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