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

Annotations already cover readOnly, idempotent, open-world and non-destructive. The description adds behavioral value beyond them: it discloses the scope constraint (US public companies only) and that 8-K material events are flagged, which hints at the curation of results.

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?

Two tight sentences: the capability and its contents are front-loaded, followed by the required input. 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?

An output schema exists, so return values need not be documented, yet the description still summarizes them usefully. With one 100%-covered parameter and full annotations, it is nearly complete; the only gap is explicit routing guidance among the brief_* siblings.

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 coverage is 100% with a single well-described parameter, so the schema carries the load. The description's 'ticker, name or CIK' merely restates the parameter description rather than adding new meaning; 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 ('briefs') and resource ('US public company') and enumerates what the brief contains (SEC profile, filings, insider trades, financials). The 'US public' scoping and the entity type distinguish it from brief_domain, brief_place and brief_stack without opening any schema.

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?

Usage is implied by the 'One call briefs you' framing and the sibling family, but there is no explicit when-to-use or when-not guidance. It tells you the input formats but not when to choose this over brief_domain or koot_watch.

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