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

Annotations already declare readOnlyHint and idempotentHint, so no safety concern needs repeating. The description adds valuable behavioral context beyond annotations: it aggregates multiple filing types, returns rows that link to SEC filings, and provides next_tools for follow-up. This helps an agent know what to expect from the call.

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 compact and front-loaded with 'START HERE,' then efficiently lists the contained data categories and the row-link behavior. No sentence is wasted; each adds selection or invocation 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 2-parameter read-only aggregation tool with no output schema, the description is complete enough. It tells the agent what data comes back, that rows link to filings, and how to proceed for deeper questions. The schema covers input parameters, so nothing essential is missing.

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 the schema fully documents query and window_days. The description adds little parameter-level meaning beyond mentioning 'ticker or company name,' which is already in the schema. The baseline of 3 applies because structured fields carry the parameter semantics.

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 verb and resource: one call returns the full insider picture for a ticker or company name, enumerating 13D/13G, Form 4, Form 144, and 8-K data. It also distinguishes itself from sibling tools by explicitly presenting itself as the starting point and noting that deeper questions are routed via next_tools.

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 gives clear routing guidance: use this as the START HERE tool for any company question and follow next_tools for deeper dives. It does not explicitly name alternatives or state when not to use it, but the entry-point framing is a strong usage signal.

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