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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is already covered. The description adds that records span Form 3/4/5 and lists returned fields, but doesn't mention recency semantics, data freshness, or pagination behavior. With annotations carrying the safety load, a 3 is appropriate.

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 sentences, front-loaded with the core action and result fields, followed by routing guidance. Every clause earns its place; no filler.

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?

Given that an output schema exists (agent needn't explain return values), annotations cover read-only/open-world, and schema coverage is 100%, the description is nearly complete. Minor gap: it doesn't state a default or max for limit, though the schema already does. A 4 reflects a strong, almost fully specified definition.

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 100%, so the schema already documents cik, ticker, and limit. The description only names the two lookup keys and doesn't add format constraints (e.g., CIK zero-padding rules) beyond what the schema provides. Baseline 3 is correct when schema does the heavy lifting.

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), resource (SEC Form 3/4/5 insider-transaction records), and scope (for a company by cik or ticker). It also enumerates the fields returned (owner, role, security, shares, price), distinguishing it from sibling SEC 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?

Explicitly names three alternative sibling tools (sec_company_intelligence, sec_filing, sec_institutional_holdings) and describes the condition each is better suited for. This is textbook when-to-use-vs-alternative guidance.

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