v2_alerts

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful context that this is the alert-flagged subset of events, but says nothing about pagination, default limits, or the default time window.

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?

A single sentence that front-loads the resource identity before listing filters, with no filler. It is efficient, though the parenthetical clarification slightly interrupts the filter enumeration.

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 read-only listing tool with no output schema and annotations covering safety, the core identity and most filters are conveyed. Still, the omission of limit and siteId and the absence of default/pagination behavior leave gaps for an agent invoking it 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 description coverage is 0%, so the description carries the burden and does name most filter dimensions: archived/unarchived, level, module, time window (hours), and search. However it omits limit and siteId entirely and gives no value formats, enum meanings, or defaults for the filters it does name.

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 resource ('Site ALERT log') and clarifies its scope as the subset of events flagged as alerts, which distinguishes it from the v2_events sibling. The verb is implicit (a log to be listed/retrieved), so it is clear but not maximally sharp.

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 implies the tool is for browsing alerts but gives no explicit when-to-use guidance, prerequisites, or named alternative such as v2_events for the full unfiltered event stream. An agent must infer the routing decision from the word 'subset' alone.

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