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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real domain behavior the annotations cannot: these are declared intents, not completed sales, and they reappear later on a Form 4 — which matters for interpreting the data. It stops short of describing ordering/recency guarantees or what happens when no notices exist.

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 resource and scope, then the parsed payload. Every clause carries information; the only mild weakness is that the second sentence is a dense list that reads as a fragment.

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 carries the return-value burden and does it well by enumerating parsed fields: seller, issuer relationship, and per-block shares, aggregate market value, approximate sale date, exchange and broker. Minor gaps remain around empty results and whether notices are historical or pending-only.

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%, with both ticker and limit documented inline including the 1-100 range and default of 8. The description adds no parameter-level detail beyond what the schema already supplies, so the baseline 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?

The description names a specific resource (Form 144 notices) and scopes it to a ticker, then defines the resource in domain terms: an insider's declared intent to sell restricted or control stock. It implicitly separates itself from Form 4 by stating these notices are filed before the sale and later appear on a Form 4, but it never names a sibling tool outright.

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?

Timing is implied through the lifecycle note ('filed before the sale executes and later shows on a Form 4'), which hints this is the pre-sale intent source rather than the executed-transaction source. There is no explicit when-to-use or when-to-use-instead statement referencing get_insider or other siblings, so the routing is left to inference.

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