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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds context about the data source (Form 4 filings) and the specific output (purchases, sales, grants, dispositions with provenance), which goes beyond the annotations without contradicting them.

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 a single, efficient sentence that front-loads the core action ('Read recent Form 4 filings for one ticker') and includes all necessary details without any fluff.

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?

The description gives a solid overview of what the tool returns, but it does not explain the behavior of the limit parameter, pagination, or response structure. Given that there is no output schema, these gaps leave the agent somewhat under-informed, though the tool is simple enough that a basic call could still succeed.

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?

The description does not mention parameters at all. Schema coverage is only 50% because limit has no description. The description fails to compensate for the missing limit explanation, leaving the agent to infer its purpose (e.g., max number of filings returned).

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 ('Read'), resource ('Form 4 filings for one ticker'), and what it returns (insider purchases, sales, grants, dispositions with provenance). This clearly distinguishes it from sibling tools like sec.filings (general filings) and congress trades, making its 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 implicitly communicates usage by specifying 'for one ticker', which tells the agent this is a single-symbol insider transaction tool. It does not explicitly mention alternatives or exclusions, but the context is clear enough that an agent would know to select it for insider transaction queries.

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