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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds useful context about the data source (SEC 8-K) and an AI summary layer, plus the scope constraint 'Public companies only,' but says nothing about pagination, rate limits, freshness, or the AI summary's reliability.

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?

Front-loaded with the resource and its distinguishing feature (AI summary), followed by usage triggers and a scope constraint in three tight sentences. No filler or redundancy.

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 read-only search with no output schema, annotations covering safety, and full schema coverage of three optional params, the description is nearly complete: purpose, content, usage, and scope are all present. It lacks only differentiation from sibling event searches and any note on result ordering or freshness.

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 days, limit, and company_name are already documented in the schema with defaults and bounds. The description adds no parameter-level meaning (e.g., interaction between days and limit, or partial-match behavior), so baseline 3 applies.

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 ('Recent SEC 8-K filings with a plain-English AI summary') and enumerates the event types covered (leadership changes, material agreements, results, restructuring). It is clear what the tool returns, but it does not explicitly differentiate from overlapping siblings such as search_major_events, search_executive_changes, or search_agreements, which cover similar event categories.

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?

Gives concrete usage triggers: 'what did company X just file' and 'to scan a window for material events.' It also states a scope limit ('Public companies only'). However, it names no alternatives and no when-not-to-use exclusions, leaving the agent to infer how it differs from the event-specific sibling searches.

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