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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the mutation profile is covered. The description adds genuinely new behavioral context beyond structured fields: that the call is FREE, hits only the database, and spends no credits because no SEO data provider is invoked.

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 sentences, front-loaded with the core action and followed by the workflow hook and cost note. Nothing is redundant and every clause carries information.

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 4-param mutation tool with full schema coverage and supporting annotations needs little more, and the description supplies the workflow linkage and cost profile. It stops short of stating overwrite semantics for an existing targetUrl or the response shape, though no output schema exists.

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% and each parameter is described there (including that null on targetUrl clears a value). The description adds only a light gloss ('the URL you intend to rank for'), so the schema does the heavy lifting and the baseline 3 applies.

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 pair (sets or clears) and a precise resource (the target URL for a tracked keyword), so the mutation is unambiguous. It also names the sibling it feeds (list_rank_cannibalisation), letting an agent place it in the workflow without opening the schema.

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?

Gives clear context: set this for the keywords you care about, then check for a mismatch via list_rank_cannibalisation after the next run. It lacks an explicit when-not-to-use or a named alternative for edge cases, but the workflow trigger is well conveyed.

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