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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds valuable behavioral context: it explains that the inline list is a preview capped at limit, that the full set is materialized as a dataframe when a canvas is available, and that filings are scanned newest-first. It also clarifies the scope of transaction types (nonDerivative vs derivative). The only minor gap is not explicitly stating that the tool is read-only, but annotations cover that.

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 dense but well-structured, front-loading the core purpose and return fields before diving into usage nuances. Every sentence adds value, though it is slightly long. The SQL example and sibling reference are useful but could be trimmed without losing essential information. Still, it's efficient for the complexity it covers.

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?

Given the tool's complexity (3 params, output schema, canvas integration, sibling tools), the description is remarkably complete. It covers what the tool returns, how to use the dataframe for aggregation, when to use an alternative, and the filtering semantics. The output schema exists, so return values are already documented. Nothing critical is missing for an agent to call this 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 description coverage is 100%, so the schema already documents all three parameters well. The description adds extra meaning by explaining the transaction_type filter semantics (e.g., 'purchase' = open-market buys code P, 'sale' = open-market sells code S, 'all' includes grants, awards, exercises, gifts) and clarifies that ticker_or_cik refers to the issuer, not the reporting person. This goes beyond the schema's basic 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 clearly states the tool fetches Form 4 insider transactions by parsing SEC EDGAR ownership XML, enumerates the exact data fields returned (reporting person, relationship, date, type, shares, direction, price, post-transaction ownership), and distinguishes it from sibling tools like secedgar_search_filings. The verb 'Fetch' plus the specific resource 'Form 4 insider transactions' makes the purpose unambiguous.

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 explicitly tells when to use this tool versus alternatives: 'Use secedgar_search_filings with forms=["4"] for broader date-range queries or to search across all companies.' It also explains the canvas materialization and how to query the resulting dataframe with secedgar_dataframe_query, including a SQL example. This is exemplary guidance.

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