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

Annotations already mark the operation read-only, and the description adds useful behavioral context: Form 4 source, one-company scope, newest-first ordering, and trade-code meaning. It doesn't cover rate limits or auth, but those are not critical with readOnlyHint=true.

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?

Three short sentences carry scope, output details, usage guidance, exclusion, and an argument list. There is no filler and key information is front-loaded.

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 an output schema present, return values need not be spelled out; the description covers scope, ordering, code semantics, and sibling routing. The only notable gap is that start/end/limit are not semantically described, though schema types/defaults partially cover them.

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 0%, but the description only lists argument names (entity; start; end; limit). It implies entity is a company but gives no format or semantics for start/end or how limit behaves, so it fails to compensate for the empty schema descriptions.

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 states the action and resource clearly: Form 4 insider transactions for one company, with specific output fields and newest-first ordering. It also differentiates from get_congress_trades, so an agent can distinguish it from siblings.

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 explicit when-to-use examples (insiders buying X, CEO selling, insider activity) and an explicit exclusion with the sibling to use instead (Congress -> get_congress_trades). This is unambiguous routing guidance.

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