Get latest insider trading alerts

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint false. Description adds valuable context: default minScore=80 (high-confidence), returns both Form 4 and 8-K alerts, and scope defaults to universe. No contradictions with annotations.

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?

Four sentences, each adding distinct value: purpose, default behavior, usage guidance, sibling differentiation. No fluff or redundancy. Information is front-loaded.

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?

Coverage is strong for a read-only listing tool with rich annotations and 100% schema coverage. Description covers main purpose, defaults, and when to use sibling. Lacks explicit mention of output format (e.g., array of alert objects), but this is minor given no output schema and context signals indicating it.

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% (all 6 parameters described). Description adds clarity on minScore default and its effect on confidence threshold, and mentions scope default ('universe'). These details go beyond the schema annotations for default values.

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?

Description specifies verb 'returns', resource 'latest SEC Form 4 and 8-K Item 5.02 alerts', and scope 'ranked by recency'. Clearly distinguishes from sibling edgaralert_search_alerts by contrasting use cases. No ambiguity.

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?

Explicitly states when to use: 'what's happening right now' questions. Directly names alternative tool for complex searches: edgaralert_search_alerts. Provides clear context for tool selection.

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