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

With no annotations, the description carries the full burden and does meaningful work: it discloses ingestion latency (~1 minute after SEC acceptance), that wait= blocks the request until a filing lands, and that cursor results come back oldest-first. It omits auth/credential requirements and rate limits, but the latency and long-poll semantics are exactly the kind of trait annotations would otherwise supply.

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 purpose and example, but the first sentence is duplicated verbatim ('Structured SEC filings feed ... — Structured SEC filings feed ...'), which is pure waste in an otherwise short description. The remaining sentences are reasonably efficient.

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?

For an 8-parameter, no-required, no-output-schema feed tool, the description covers what the resource is, how to filter it, both retrieval modes (cursor paging and long-poll), and freshness latency. Missing pieces such as auth expectations and response envelope details are minor given the schema fully documents the inputs.

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%, so every parameter (cik, days, form, item, wait, limit, since, ticker) is already documented in the schema. The description only restates the filter fields and paging/cursor concepts at a high level, adding no syntax, format, or edge-case meaning beyond the 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 resource and scope: a structured SEC filings feed covering named form types (8-K, Form 4, Schedule 13D/13G, 10-K, 10-Q), with filtering and paging modes. An agent can tell this is the general filings feed, but the description never distinguishes it from siblings like filings_8k_events, filings_freshness, or filings_latest_preview, which overlap heavily with its stated scope.

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 describes operational modes ('page with a cursor, or long-poll with wait=') which implies when to use each, and gives a concrete example query. But there is no explicit when-to-use guidance against alternatives and no exclusions, so the agent must infer the routing from sibling names alone.

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