Proposed Insider Sales (Form 144)

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

Annotations only declare readOnlyHint=true, and the description adds real behavioral context: results are ordered most-recent-first, a note flags when more exist than were returned, and it cautions that a proposal may never execute and only appears on Form 4/5 when reportable. It does not spell out offset/pagination mechanics explicitly, but the truncation note covers the key risk.

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 packs returned fields, ordering, and caveats into one dense paragraph with little waste. It is on the longer side, but each clause carries actionable information rather than 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?

With no output schema, the description enumerates the returned fields (seller, relationship, shares, aggregate value, percentage of shares outstanding, sale date, broker, remarks/10b5-1) and covers ordering, truncation, and interpretation caveats. An agent has everything needed to call and interpret it correctly.

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 baseline is 3, but the description earns a step up by explaining the purpose of fromDate/toDate (scoping a period to avoid 10b5-1 flooding), which adds decision value beyond the schema's format hints.

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 and resource ('Get recent proposed insider sales ... from SEC Form 144 notices') and effectively differentiates from the Form 4/5 tools by clarifying these are declarations of intent, not completed sales. An agent can distinguish this from GetInsiderTransactions 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?

Gives clear context on when to scope with fromDate/toDate and warns that heavy 10b5-1 filers can flood the recency window with small daily notices. It stops short of naming an alternative sibling tool or stating explicit when-not conditions, so it is clear but not fully routing.

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