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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds nothing on top of that — no statement about irreversibility, cascade effects, required permissions, or confirmation requirements. It merely repeats the destructive verb that the annotations already encode.

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 short, front-loaded sentence with no filler, so there is nothing wasteful to trim. However, it is concise to the point of being under-specified rather than efficiently informative.

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 destructive, zero-annotation-detail, three-required-parameter operation with no output schema, the description should at minimum identify the resource boundary and the irreversibility of the action. It leaves the agent without the information needed to invoke it confidently.

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% and the description says nothing about projectId, siteId, or keywordId. The identifiers are somewhat self-describing by name, but the description contributes zero semantic value for a tool that requires all three correctly scoped IDs to avoid deleting the wrong record.

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 is essentially a restatement of the title ("Delete a lead keyword" vs "Delete a monitoring keyword"), swapping in a different noun for the resource. It never clarifies which entity is being deleted (a lead keyword vs. an outreach or article keyword) or how it differs from the many sibling delete_* and remove_* tools. Without opening the schema an agent cannot tell why it should pick this over remove_outreach_keyword or delete_lead_alert_rule.

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 when-to-use guidance, no prerequisites, no mention of alternatives, and no warning that this is an irreversible removal. For a destructive tool in a family containing several near-identical keyword deleters, this omission is actively unhelpful.

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