Search insider trading alerts with filters

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds context about the required subscription plan and the query scope, but does not discuss response format or pagination. Since annotations are rich, the description supplements them well without contradiction.

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, each serving a distinct purpose: the first explains the tool's function and lists key filters, the second gives usage guidance and an alternative. No wasted words, and the core action 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?

For a tool with 16 parameters and no output schema, the description provides a good overview of capabilities, usage context, and prerequisites. It does not describe the output structure, but the limit parameter hints at pagination. Overall, it is fairly complete for an experienced user.

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 each parameter is already documented. The description adds value by grouping filters into categories (e.g., 'signal score range, date range, transaction side'), but does not provide details beyond what the schema offers. Baseline 3 is appropriate.

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 action ('Searches SEC insider trading alerts'), specifies the resource (Form 4 and 8-K events), and distinguishes itself from the sibling tool edgaralert_get_latest_alerts by contrasting 'targeted research questions' with 'general recent-activity feed'.

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 defines when to use ('targeted research questions') and when not to use ('general recent-activity feed'), names the alternative tool (edgaralert_get_latest_alerts), and mentions the prerequisite (PRO plan or higher, noting the Enterprise key qualifies).

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