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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered by structured data. The description adds the quoting convention but says nothing about EDGAR rate limits, pagination, result ordering, or what a result record contains – meaningful gaps for an open-world remote search.

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?

A single front-loaded sentence with no wasted words. It is efficient, though that brevity is part of why behavioral and return-shape information is missing.

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 open-world search with no output schema, the description leaves the agent unsure what comes back (filing list with URLs? snippets?) and how paging works. The schema carries most parameter meaning, but the description does not fill the return-value gap.

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 86%, so the schema already documents q, cik, ticker, forms, and date formats; the description's 'quote exact phrases' and 'filter by form and date' merely restate it. Nothing is said about limit (default 20, max 100) or how cik/ticker interact, so no value is added 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 verb and resource – 'full-text search across EDGAR filings' – which is clearly distinct from sec_company_filings or sec_company_search. It does not name or contrast any sibling, so an agent must infer the boundary between this and sec_company_filings itself.

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?

Implies usage through 'quote exact phrases' and 'filter by form and date', which tells the agent what the tool is good for but not when to prefer it over sibling tools like sec_company_filings or federal_register_search. No explicit when-to-use or when-not-to-use guidance is given.

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