search_alerts

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

With no annotations, the description carries full burden. It describes parameter behavior (e.g., tags require all matches) but lacks details on pagination, maximum limit, authentication needs, or error handling. There is no contradiction 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?

The description starts with a clear one-line purpose, followed by a well-structured bullet list for parameters. While the list is long, each parameter has a brief but informative explanation. No unnecessary 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 covers all parameters adequately but lacks contextual information such as pagination behavior, result handling (empty list vs null), and any constraints on the limit parameter. Given the presence of an output schema, return values need not be detailed, but behavioral completeness is moderate.

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 0%, so the description compensates well. It explains the meaning of each parameter beyond schema type/defaults: substring match for title, exact level for severity, AND logic for tags, examples for status, sorting syntax with '-' prefix, and date formats. Missing details on tags being a list of strings (but schema provides that).

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 'Search for Alerts in TheHive with advanced filtering', which is a specific verb-resource combination. It distinguishes from siblings like get_alert (single alert retrieval) and search_cases (cases vs alerts).

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?

No guidance is provided on when to use this tool versus alternatives like get_alert or search_cases. The description only explains what the tool does, not the context for choosing it.

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