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

Annotations already cover the safety profile (destructiveHint=true, readOnlyHint=false, openWorldHint=false), so the description only needs to add nuance. It adds nothing — no statement of irreversibility, no cascade behavior, no confirmation semantics — so it contributes zero beyond the structured fields.

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 single sentence is free of filler, but it is under-specified rather than concise — it conveys no information an agent could not derive from the tool name. Brevity here reflects a content gap, not efficiency.

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?

A destructive, no-output-schema delete with three undocumented required IDs is missing the essentials: irreversibility warning, required permissions, and how to obtain the identifiers. Only the annotations carry any behavioral weight.

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?

Three required parameters (projectId, siteId, ruleId) with 0% schema description coverage receive no explanation in the description. It does not say where these identifiers come from or how they relate to the alert rule hierarchy.

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?

'Delete an alert rule' restates the name and title almost verbatim with no additional verb, scope, or distinguishing detail. With siblings like delete_lead_icp, delete_lead_keyword, and delete_outreach_template following identical naming, the agent gains nothing beyond the tool name itself.

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 when-to-use guidance, no mention of prerequisites, and no reference to the sibling list_lead_alert_rules that would supply the ruleId. The agent must infer the entire workflow from the name.

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