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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond that: the response includes all transaction legs, holdings, and footnotes, signalling a comprehensive payload rather than a summary. It omits any error behavior for a malformed accession, keeping it short of a 5.

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?

A single front-loaded sentence naming the resource, the key, an example, and the payload contents — no filler and nothing buried.

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?

With no output schema, the description correctly compensates by enumerating what the filing payload contains (transaction legs, holdings, footnotes). The annotations cover safety, and the input format is documented in both schema and description. Only error handling for bad accessions is left unstated.

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?

There is one parameter with 100% schema description coverage, and the schema already documents both accepted forms (dashed or dashless archive-URL). The description only repeats an example accession, which is duplicative rather than additive, so the baseline of 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 (fetch), a precisely scoped resource (one insider ownership filing, Form 3/4/5), and the exact lookup key (SEC accession number) with a concrete example. This is clearly distinguishable from the plural-scanning sibling get_insider_trades without opening either 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 required accession-number input and the example format, so an agent can infer this is the single-filing lookup. However, the description never states when to prefer this over get_insider_trades or get_corporate_events, and names no alternatives or prerequisites.

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