Search Filing Text

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

Annotations declare readOnlyHint=true, consistent with non-destructive search. Description adds behavior: substring match, case-insensitive, minimum 2 characters (from schema), and returns snippets with context. Does not mention rate limits or pagination, but output schema exists.

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?

Three sentences covering action, output, and filtering options. Front-loaded with main purpose. No wasted words.

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?

Covers essential aspects: what it searches, what it returns, filtering options, and typical use cases. Missing pagination or default limit, but schema covers limit parameter and output schema exists. Sufficient for a search 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 100%, so parameters are technically documented. Description adds usage context: examples of search terms, mention of filtering by company/filing/form type, and what snippet length does. Adds value beyond 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?

Clearly states full-text substring search across SEC filing exhibit content, distinguishing it from siblings like get_exhibit_content (full exhibit retrieval) and search_sec_filings (metadata search). Examples of specific clauses reinforce purpose.

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?

Provides examples of when to use (finding specific clauses) and mentions optional filters (CIK, form type, etc.), implying when to narrow searches. Does not explicitly contrast with all siblings but context signals and sibling names help differentiation.

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