Get SEC Filing Calendar

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

Annotations declare readOnlyHint: true, and the description uses 'Get', aligning with a read-only operation. The description does not add any behavioral traits beyond what annotations already provide, so a baseline score of 3 is appropriate.

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 two concise sentences, front-loaded with the core purpose, and no extraneous information. Every word serves a purpose.

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 that the tool has 0 required parameters, 100% schema coverage, an output schema, and readOnlyHint annotations, the description covers all necessary context. It explains the core function and optional filters, which is complete for an AI agent to use 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%, and the tool description briefly summarizes the parameters (date window, universe, formTypes) and their defaults. However, it does not add significantly more meaning than the schema itself, so baseline 3 applies.

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 'Get the forward-looking 10-K / 10-Q SEC filing-deadline calendar', specifying the verb (Get), the resource (filing-deadline calendar), and scope (within a date window). This distinguishes it from sibling calendar tools like get_earnings_calendar or get_economic_calendar.

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 explains the optional filters (universe, formTypes) and implies this is the tool for SEC filing deadlines. It does not explicitly state when not to use it or list alternatives, but the context is clear enough for an AI agent to differentiate from other calendar tools.

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