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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered. The description adds value beyond them by declaring the effect is immediate and irreversible, which an agent needs to weigh before calling. It does not mention auth/permission requirements or error behavior, keeping it from a 5.

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?

Two tight sentences with no filler; the destructive consequence is front-loaded and the id source follows. Every clause earns its place.

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 one-parameter destructive tool with full annotations and no output schema, the definition covers purpose, irreversibility, and id sourcing. It omits only permission requirements and any failure modes, which are minor gaps here.

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 100% on the single id parameter, setting a baseline of 3. The description adds provenance the schema lacks ('Get the id from list_spotlight_rules'), telling the agent how to obtain a valid value rather than only what the field means.

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?

Specific verb (delete) plus resource (a rule), and it goes further by stating the consequence ('stops applying at once and cannot be restored'), which separates it from reversible siblings like set_spotlight_rule_enabled and update_spotlight_rule. An agent can tell instantly this is a permanent removal, not a disable.

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 routes the agent to list_spotlight_rules as the source of the id, giving a concrete precondition for invocation. It implies but does not explicitly state the alternative path for reversible action (disable via set_spotlight_rule_enabled), so it falls slightly short of full when-to-use/when-not guidance.

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