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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds only that results are paginated — useful, but it omits default sort order, what a trade record contains, and whether all 9 filters are ANDed together, which matters for a query with this many optional parameters.

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?

Two short sentences with zero waste: the retrieval scope and filter dimensions come first, and the pagination note follows. Nothing is repeated and nothing extraneous is included.

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 9-parameter, zero-required query tool with no output schema, the description covers the query surface and pagination adequately, and annotations carry the safety profile. It is still thin on what is actually returned per trade (fields, units, currency) and on how multiple filters combine, both of which the agent must infer.

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 every parameter including cursor, limit, and the four date bounds is already documented in the schema. The description's list of filter dimensions ('ticker, trade type, value, and date ranges') only restates the schema at a higher level and adds no combination logic or format detail.

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 (retrieve insider trades) and enumerates the filterable dimensions (ticker, trade type, value, date ranges), so an agent knows exactly what data it returns. It does not, however, distinguish itself from the closest sibling get_insider_sentiment or from get_politician_trades, which an agent could plausibly confuse with this one.

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 says what can be filtered but never states when to choose this tool over get_insider_sentiment, get_politician_trades, or get_stock_ownership, and gives no prerequisites or exclusions. Usage is only inferable from the purpose statement, matching the 'no when-to-use guidance' calibration case.

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