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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the response includes specific fields and that it is for one exact ticker, which is useful context. However, it does not disclose pagination behavior (though limit/offset are in the schema), error handling for invalid tickers, or any rate limits. It adds some value but does not go beyond what the annotations and schema already convey.

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 of about 20 words, front-loaded with the action and resource, and efficiently lists the returned fields. There is no filler or redundancy; every word adds value.

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 a simple read-only list operation with three parameters (one required), the description is largely complete. It states the scope (single ticker), the recency (recent), and the fields returned. It does not mention pagination explicitly, but that is captured by the schema defaults. Since there is no output schema, the description's field enumeration is helpful. Minor omissions like empty-result behavior are acceptable for this type of tool.

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 only 33% (only ticker has a description). The description does not compensate for the undocumented limit and offset parameters. While those are standard pagination parameters, the description doesn't explain their semantics, defaults, or maximums. The phrase 'one exact ticker' reinforces the ticker schema description but adds little beyond it. Given the low coverage, the description should have clarified limit and offset but didn't.

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 a specific action ('List') on a specific resource ('SEC filings') with a specific scope ('one exact ticker') and enumerates the returned fields (filing date, acceptance timestamp, form, accession, source URLs). This distinguishes it from sibling tools like sec.thirteenf_holders or sec.insider_transactions, which target specific filing types.

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 a single ticker ('one exact ticker') and implies a time-bound set ('recent'), but it does not explicitly state when to prefer this over alternatives or when not to use it. There is no mention of exclusions, such as 'for 13F filings use sec.thirteenf_holders' or 'for broader market data use market.history.' The guidance is adequate but not explicit.

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