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

Annotations already establish a safe read-only, idempotent operation, and the description adds substantive behavior: it pulls live EDGAR data, classifies 8-K item codes into seven categories, and computes a score and action hint. This goes beyond the structural hints without contradicting them. It stops short of explaining failure modes or data freshness, but the live-source caveat is helpful.

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 two-sentence description is compact and front-loaded with the SEC/EDGAR anchor before listing outputs. Minor redundancy, such as '8-K' and 'public company' appearing twice, keeps it from being perfect, but every sentence earns its place.

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 no output schema, the description does communicate the key return elements: score range, dominant theme, and buyer-tuned action hint. It also names the filing source and change categories. Gaps remain for limit/window_days semantics and the exact output shape, so the description is useful but not fully complete.

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%, so the description needed to compensate. It does clarify buyer_profile by listing its values and tying it to the action_hint output, and domain/ticker are already described in the schema. However, limit and window_days remain wholly unexplained beyond their raw min/max/default constraints.

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 names a specific resource (SEC 8-K filings from EDGAR) and a precise processing pipeline: classify item codes into change categories and return a change-velocity score, theme, and action hint. This makes the tool's purpose unmistakable. However, it never explicitly distinguishes itself from near-siblings like company_changes or company_signal, so it falls short of a 5.

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 implies use cases through 'buyer-shaped action_hint tuned by buyer profile' with enumerated profiles like sales_outreach and recruiter, which tells an agent roughly when this tool is valuable. But it provides no explicit when-to-use/when-not-to-use guidance and does not name alternative tools or exclusion conditions.

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