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

With no annotations, the description carries the full burden and does meaningful work: it warns that latest.net_severity is a sum of deterministic disclosure-change scores and explicitly not financial impact, that latest.brief has an undetermined direction and empty top_themes, and that legacy AI judgments are withheld. These caveats prevent misreading the payload. Gaps remain on pagination, ordering, and auth/rate behavior.

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?

Three sentences, front-loaded with the action and contents, then narrowing to the two fields most likely to be misread. Every clause carries a caveat rather than restating the name. The dense dotted field references make it slightly harder to scan but add precision.

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?

No output schema and no annotations exist, so the description is the only source of payload semantics, and it covers the ambiguous parts (net_severity, brief, withheld judgments). It does not describe how the 'available 10-K comparison years' are represented, nor list ordering, so it is strong but not exhaustive for a zero-param listing tool.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its space on return-value semantics, which is a sensible allocation.

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 leads with a specific verb and resource ('List all tracked companies') and enumerates what each entry carries: 10-K comparison years plus a disclosure overview for the latest filing. That distinguishes it from the sibling diff/signal tools, which operate on a single company or signal. It stops short of naming those siblings explicitly.

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?

There is no statement of when to call this versus get_company_diff, list_company_diffs, get_signal, or list_signals, and no prerequisite/ordering guidance. The role as a discovery/entry point is only inferable from the word 'List all'. No exclusions are given.

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