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

With no annotations, the description carries the full burden. It discloses the filtering capabilities and declares it is for monitoring/research only, but does not mention rate limits, authentication, idempotency, or potential side effects. Basic behavioral context provided.

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 concise at three sentences, front-loaded with the core function. The phrase 'core lock-in primitive' is somewhat jargon-y but does not detract significantly. Well-structured for quick comprehension.

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 7-parameter tool with no output schema, the description explains the cursor mechanism and filters but lacks details on output format, pagination behavior, default values (e.g., limit default 100), and how to obtain the initial cursor. Adequate but not comprehensive.

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?

71% schema description coverage; the description lists filter parameters (form, ticker, etc.) but does not add detailed semantics beyond what the schema already provides. Parameters without schema descriptions (cik, ticker) are mentioned but not explained further, so only marginal added value.

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 that the tool returns new SEC filings since a cursor token, with a specific verb 'Return' and resource 'SEC filings'. It distinguishes itself from sibling tools by emphasizing the delta feed mechanism, making the purpose unambiguous.

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 iterative usage with the cursor but does not explicitly state when to use this tool versus alternatives like search_filings or insider_activity. No guidance on prerequisites or scenarios to avoid.

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