search_alerts

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

With no annotations, the description carries the full burden. It explains filter syntax, date formats, and server selection. However, it does not disclose pagination behavior, sorting details, output format, or whether the operation is read-only. This leaves gaps in behavioral understanding.

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 fairly concise and structured with clear sections for filters and timestamps. It uses bullet-like formatting but includes an example, which is helpful. Minor redundancy (e.g., repeating 'optional list of filter objects') but overall efficient.

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 7 parameters, no schema descriptions, and an output schema (not shown), the description covers only filters, timestamps, and server. It misses pagination (page, size) and sorting (sort), and does not describe the return structure. This leaves significant gaps for an agent to use the tool 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 coverage is 0%, so the description must add meaning. It explains filters (operators, useful fields), start/end (relative/absolute), and server. However, it omits explanation for page, size, and sort parameters, which are present in the schema but undocumented.

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 alerts in the v11-alert-* index,' which specifies a verb and resource. However, it does not differentiate this tool from siblings like search_logs or get_alert, preventing a score of 5.

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 provides details on how to use filters and timestamps, implying when the tool is appropriate (searching alerts). But it lacks explicit guidance on when not to use it or alternatives, such as using get_alert for a single alert or search_logs for logs.

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