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

With no annotations, the description carries the behavioral disclosure burden and does so well: it explains the data source, the code-P-only filter, the exclusion rationale, and the meaning of observed_at versus happened_at. It does not cover ordering, pagination, or rate limits, but those are minor for a simple read-only feed.

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?

The description is compact and front-loaded: scope, exclusion rule, rationale, field semantics, and sibling routing each get one clear sentence. There is no redundant or promotional language.

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?

For a three-optional-parameter read feed with no output schema, the description provides enough context for an agent to decide when to use it and what it returns. The only minor gap is lack of detail about default result ordering or size limits.

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?

The schema already documents since and min_value, and the description does not add parameter-level meaning beyond that. The ticker parameter has no schema description and is not mentioned in the tool description, but its meaning is obvious from the context, so the 67% schema coverage is adequate.

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 clearly identifies the tool as a feed of SEC Form 4 open-market insider buys and immediately narrows it to code P transactions. It explicitly excludes grants, option exercises, tax withholding, and gifts, and names the sibling insider_sells for disposals, making the purpose distinct.

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?

It states when this feed is appropriate: when an officer or director spends their own money, i.e., conviction buying. It also gives a direct alternative, telling agents to use insider_sells for disposals, and clarifies which transaction types should not be queried here.

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