sec8k_material_today

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

The description provides minimal behavioral information. It does not disclose whether results are real-time, if authentication is needed, or what happens when no filings match. Since no annotations exist, the description carries the full burden, and it falls short.

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 a single, front-loaded sentence that efficiently conveys the core functionality and filtering options. Slightly more structure (e.g., bullet points for item codes) could improve readability, but it is still concise and informative.

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?

The description covers the essential aspects: today's filings, filtering by item codes and ticker, and the specific codes that are material. Given the simplicity of the tool and absence of an output schema, it is sufficiently complete for correct invocation.

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% with basic descriptions. The tool description adds significant value by mapping each item code to its meaning (e.g., 2.02 = earnings), which is not present in the schema alone. This helps agents understand correct parameter values.

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 the tool retrieves material SEC 8-K filings today, filtered by specific item codes. It lists the relevant codes with brief explanations, making the purpose explicit. However, it could start with an action verb like 'Retrieve' for even greater clarity.

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 context (today's filings, specific item codes) but does not explicitly state when to use this tool versus alternatives. No guidance on when not to use or how it compares to sibling tools, which are different in nature.

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