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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive hints. The description adds meaningful context by highlighting the 'bounded' nature of the report, 'explicit section coverage', and 'official-source provenance', which go beyond the schema and annotations. No contradiction with the annotations.

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, dense sentence that front-loads the core action ('Resolve... then bundle...') and efficiently enumerates all bundled components and output characteristics. Every phrase carries meaning, with no redundancy or fluff.

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 tool with 10 parameters, low schema coverage, and distinct sibling tools, the description gives a solid high-level overview and references explicit sections and provenance, but it leaves gaps around parameter behavior, selection criteria, and practical usage constraints. The output schema covers return values, so the main deficiency is under-specification of how inputs shape the report.

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 40% (4 of 10 parameters have descriptions). The description mentions high-level data categories (filing signals, XBRL facts, Form 4), but it does not explain how parameters like max_filings, financial_periods, lookback windows, or include_derivatives control the report. It fails to compensate for the low schema coverage.

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 uses specific verbs 'Resolve' and 'bundle' to clearly state the tool's function: turning an SEC identifier (name, ticker, CIK) into a comprehensive evidence report. It explicitly lists the bundled components (filing signals, XBRL facts, Form 4 insider transactions) and distinguishes itself from sibling tools like research.sec-filing-signals and research.sec-insider-transactions by offering a combined report.

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 provides clear context by indicating this tool is for gathering a complete, bounded public-company evidence report with multiple data sections. However, it does not explicitly state when NOT to use this tool or point to alternatives for individual data types, so it lacks explicit exclusion guidance.

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