getFilingsBySymbol

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. The description adds 'direct access' but does not disclose behavioral traits like rate limits, pagination, or response structure. Without annotations, it would be insufficient; with annotations, it adds minimal value.

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 efficient sentences front-loading action and purpose. No unnecessary words, earning their place.

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?

Despite annotations covering safety, the description lacks crucial context about return format, pagination behavior, and defaults. With 5 parameters and no output schema, the description should explain what the tool returns and how results are structured.

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?

Input schema has 100% coverage with descriptions for all 5 parameters. The description adds context about filing types but does not elaborate on parameter semantics (e.g., date format, pagination). Baseline 3 is appropriate as schema does the heavy lifting.

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: search and retrieve SEC filings by company symbol. It specifies the API source and gives examples of filing types (8-K, 10-K, 10-Q), distinguishing it from sibling tools like getFilingsByCIK.

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 use when you have a stock symbol and need SEC filings, but it does not explicitly state when to use this tool versus alternatives or when not to use it. Given many siblings have similar purposes, this is a moderate gap.

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