keep_search_alerts

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that queries are CEL-based and that one alternate route is deprecated, but says nothing about pagination semantics, default page size, or what a result set contains.

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 short sentences with the core action and endpoint front-loaded; nothing is padding, though the note about the deprecated SearchEngine route is of marginal value to an agent picking a tool.

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?

No output schema exists, so the description could reasonably say what a query returns, and with five optional parameters at 20% schema coverage the gaps in limit/offset/sort semantics are real. It is adequate to invoke the tool, but not complete for an agent unfamiliar with Keep's CEL dialect.

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 only 20% (only 'cel' is documented), so the description needs to compensate and largely does not. It merely enumerates parameter names in parentheses — and even omits 'offset' — without explaining limit/offset defaults, sortable fields, or accepted sort_dir casing beyond the enum.

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 names a specific verb and resource ('Search alerts with CEL') and pins down the exact transport ('POST /alerts/query with QueryDto'). It is clear enough to distinguish from keep_get_alert or keep_list_alerts, though it never names those siblings directly.

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?

It states 'This is Keep's current query path' and that POST /alerts/search 'is not used', which is routing guidance, but that contrast is with an internal API route rather than with the sibling tools an agent actually chooses between. There is no explicit rule for when to prefer this over keep_list_alerts or keep_get_alert.

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