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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety is largely conveyed structurally. The description adds that the mutation affects *monitoring* for a single keyword, implying a reversible toggle rather than deletion, which is useful context, but it says nothing about side effects, idempotency, or what happens to collected data.

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 tight sentence with the verb pair front-loaded and no padding. It is efficient, though its brevity shades into under-specification rather than genuine economy.

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 tool with four required parameters, zero schema descriptions, and no output schema, the description is far too thin. It never names the status values or explains that project/site/keyword identifiers are all required, leaving an agent to rely entirely on the raw schema.

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 0% and the description compensates for none of it. It implies a keyword identifier ('one keyword') but never mentions projectId, siteId, or the status parameter, whose active/paused enum values are only discoverable by opening the schema.

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 action pair (pause/resume) and resource (keyword monitoring), which is clearer than the bare name. It does not, however, differentiate itself from close siblings like update_lead_keyword or delete_lead_keyword, so an agent must still infer which is the right mutation.

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 statement of prerequisites, and no mention of the alternative tools (update_lead_keyword, delete_lead_keyword) that could plausibly also change keyword state. The agent is left to guess from the tool name alone.

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