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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely new behavioral context: newest-first ordering and the transaction-code semantics (P buy, S sell, A grant, M exercise, F tax), which an agent cannot derive from structured fields. It stops short of stating pagination/limit behavior or result completeness (e.g., whether the list is truncated).

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-loaded with purpose, then triggers, then exclusions — a good ordering with no filler prose. The trailing 'Args: entity; start; end; limit' line is redundant given 100% schema coverage and is the one part that does not earn its place.

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?

An output schema exists so return values need no explanation, yet the description still names the key returned fields and code meanings. Combined with explicit triggers, exclusions, and full annotation coverage, an agent has everything needed to select and invoke 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 coverage is 100% and every parameter (entity, start, end, limit) is documented in the schema itself, so the baseline is 3. The description only restates the parameter names in an 'Args:' list without adding format, defaults, or filtering semantics beyond what the schema already says.

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+resource (Form 4 insider transactions) plus scope ('for one company, newest first') and enumerates the returned fields and code legend. This is enough to distinguish it from get_congress_trades and every other sibling without opening a 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 explicit user-phrasing triggers ('are insiders buying X', 'did X's CEO sell', 'insider activity at X') and an explicit exclusion routing to the alternative ('Not for: Congress → get_congress_trades'). Nothing about when-to-use 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.