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

Annotations already declare it is a non-read-only, non-destructive, closed-world mutation. The description adds real value with the word 'Replace', signaling overwrite semantics rather than a merge, but it does not say whether omitted fields (name, type, negativeKeywords) are reset or preserved — critical for an edit tool.

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 front-loaded sentence with no filler. It is efficient, though its brevity is partly under-specification rather than genuine concision.

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 mutation tool with a nested payload, zero schema description coverage, and no output schema, this is too thin. It omits the semantics of the replace operation and does not describe most of the writable fields an agent must populate.

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 full burden, yet it only references phrases (queries) and platforms. The name, type, negativeKeywords nested fields and the three ID parameters are left entirely undocumented.

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?

States a specific verb ('Replace') and resource ('a monitoring keyword's phrases and platforms'), so the agent knows this edits an existing lead keyword. It does not, however, distinguish itself from siblings like create_lead_keyword, set_lead_keyword_status, or delete_lead_keyword.

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 and no named alternatives. With siblings such as create_lead_keyword and set_lead_keyword_status available, the agent gets no help deciding when a full edit is appropriate versus those operations.

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