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

The readOnlyHint annotation already signals a safe read operation, so the bar is lower. The description adds useful behavioral context by defining what kind of content is returned, including the specific red-flag categories (late filings, auditor changes, selling clusters), which goes beyond the schema.

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 tight and front-loaded: data categories, usage examples, an exclusion, and the core argument summary all appear in a few short sentences. 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?

It covers the core data scope and usage triggers well, and readOnlyHint covers safety. However, with 5 parameters and no output schema, the description should at least mention start/end/limit semantics. The omission of three optional parameters makes it not fully complete for invocation.

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 0%, so the description must compensate. It names only 'entity' and 'kind' and lists canonical kind values, but it omits start, end, and limit entirely. It also does not explain date formats or the meaning of the optional parameters, leaving an agent to guess.

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 resource ('a company's own disclosures') and enumerates the data types: 8-K events, press releases, 8-K text, and governance red flags. It also explicitly distinguishes itself from 10-K/10-Q sections, so an agent can tell it apart from other filings 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?

Gives explicit trigger examples: 'any red flags at X; what did X announce; latest 8-K from X.' It also provides a clear exclusion: 'Not 10-K/10-Q sections.' This tells an agent exactly when to invoke this tool and when not to.

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