Create Alert

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

Annotations already declare a non-read-only, non-idempotent, open-world write, so the description needs to add operational context — and it adds none. Notable behaviors such as deduplication-key coalescing ("alerts sharing the same deduplication key are treated as a single alert"), actor-attribution rules, and On-Call-only fields go unmentioned at the description level.

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?

One short sentence, so nothing is bloated, but it is under-specified rather than concise — the brevity comes at the cost of any useful information about the creation payload or its gating conditions.

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 create tool with a deeply nested 20+ field payload, On-Call-gated fields, deprecated fields, and deduplication behavior, a single generic sentence is not enough. An agent cannot tell from the description what a minimally valid call looks like or which attributes have side effects.

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?

The tool takes a single `data` wrapper whose nested attributes are extensively self-documented in the schema (actor, deduplication_key, notification_targets precedence, source deprecation), so the schema carries the semantics. The description adds no parameter meaning whatsoever, leaving it at the baseline for a schema-rich tool.

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?

It states a verb and resource ("Creates a new alert"), which is clear enough on its own, but the trailing "from provided data" is filler and the description never distinguishes this from nearby siblings such as create_alert_group, create_alert_event, or attach_alert.

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?

There is no guidance about when to create an alert versus creating an alert event, attaching an existing alert, or adding it to an alert group. No prerequisites (API key scope, On-Call enablement) are mentioned even though several schema fields are gated on them.

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