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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral scope by specifying open-market trades only, across all companies, with totals, though it does not discuss authentication, rate limits, or pagination.

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 two sentences and front-loads the core action. Examples follow immediately and every sentence earns its place without repetition.

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 rich annotations, full schema coverage, and an output schema, the description provides enough context to call the tool correctly. The only meaningful gap is not clarifying how this differs from closely related sibling tools such as get_insider_activity.

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 schema already documents name, days, and limit. The description adds contextual meaning around insider roles and partial-name matching via examples, but does not add parameter-specific details beyond what the schema provides.

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 a specific verb and resource: find an insider by name and list their open-market trades across all companies, with totals. It distinguishes the tool as person-centric, but does not explicitly name sibling alternatives such as get_insider_activity or find_insider_buying.

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?

The description gives clear example use cases ('what has Warren Buffett bought recently?' and 'Jensen Huang stock sales'), which tells the agent when this tool is appropriate. However, it provides no when-not guidance or explicit comparison to sibling tools like get_insider_activity.

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