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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavioral context beyond that: the source is efts, it is credential-free public data, and results are paginated. It stops short of describing rate limits or result ordering.

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?

Front-loaded with the core behavior and ends with the disambiguation cue, which is the right ordering. Some sentences repeat schema parameter descriptions verbatim, which is mild waste but not harmful.

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?

With an output schema present, return values need not be explained, and the description covers source, filtering, pagination, auth status, and the sibling alternative. Complete enough to invoke correctly, with only minor gaps around result volume or ordering.

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%, so from/to/forms/page are already documented in the schema. The description restates q (quoted phrases) and page (1-based, default 1) verbatim from the schema, adding no extra syntax or semantics. Baseline 3 for a fully-covered schema.

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?

States a specific verb (searches) and resource (full text of SEC EDGAR filings) plus the scope (filtered by form and date, with pagination). It explicitly distinguishes itself from the sibling sec_filing, which retrieves a single filing.

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?

It names the alternative (sec_filing) and the condition that selects it ('to get a single filing by accession number'), which routes the agent correctly. It does not, however, state when full-text search is the wrong choice versus other SEC siblings like sec_company_search.

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