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

Annotations already cover readOnly/idempotent/openWorld, so the bar is lower. The description adds genuine operational context beyond them: ~once-per-minute refresh cadence, newest-filed-first ordering, and a 100-row ceiling. It stops short of documenting rate limits or pagination behavior in depth, so not 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?

Front-loads the purpose and data source, then packs the field list and defaults efficiently into essentially two sentences. The mid-sentence return-field enumeration is long but informative rather than wasted; slightly dense but well organized.

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 usefully enumerates returned fields, plus cadence, ordering, row cap, and default filters. For an 11-parameter read tool with full schema coverage this is close to complete; only paging depth and sibling routing are left implicit.

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 all 11 parameters including code meanings, ranges and defaults. The description only restates the default code set (P,S) and 7-day window, adding no syntax or semantics beyond the schema. 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 resource (SEC Form 4 insider transactions from EDGAR) with a clear verb (list/latest) and enumerates the returned fields. This is readily distinguishable from siblings like cluster_buys (aggregated signal) and data_status (system status). An agent knows exactly what it retrieves without opening the 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?

The description implies usage through its defaults ('open-market buys and sales filed in the last 7 days') but never states when to choose this over cluster_buys or data_status, nor any when-not conditions. Guidance is inferable from defaults, not explicit.

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