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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds context by specifying that events are 'deterministic' and enumerating the event types, which goes beyond the annotations. It does not mention rate limits, failure modes, or data freshness, but the added detail about deterministic rules is useful.

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 sentence with a clear action chain (look up, normalize, flag) and front-loaded with the primary input and purpose. There is no extraneous information, making it highly concise and well-structured.

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 core functionality: input type (ticker/CIK), normalization behavior, and output event categories. Since an output schema exists, return details are not required in the description, and annotations handle safety. The description is sufficiently complete for a read-only research tool, though it omits how the forms filter interacts with event detection or what normalization entails exactly.

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 50%: identifier and forms have descriptions, while max_filings and lookback_days do not. The description mentions 'ticker or CIK' and 'recent SEC filings', loosely covering identifier and time window, but does not explain the remaining parameters or add specific semantic detail beyond the schema, leaving the agent to infer from parameter names.

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's function: look up a company, normalize filings, and flag deterministic events like late filings, amendments, auditor changes, non-reliance, control changes, or bankruptcy. It uses specific verbs and differentiates from sibling SEC research tools by emphasizing event signals rather than company evidence, financial facts, or insider transactions.

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 detecting SEC filing events but provides no explicit 'use when' or alternative-tool guidance. It does not explain when to choose this tool over siblings like research.sec-insider-transactions or research.sec-company-evidence, so the agent must infer the appropriate context from the purpose statement.

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