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

Annotations declare readOnlyHint=false, so this is a mutating/job-launching call, yet the description's verb 'Scan' reads as a passive read and never says that improvement records are created, whether the work is async, or how long it takes. The presence of an idempotencyKey parameter also implies retryable creation semantics that the description never explains. Not a strict contradiction, but the description undersells the mutation.

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 or repetition. Efficient, though the brevity is partly under-specification rather than disciplined 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 3-required-param, mutating, likely long-running scan with no output schema, the description is missing the essentials: what it creates, whether results arrive synchronously or must be fetched via get_article_improvements, and why an idempotency key is mandatory. An agent could invoke it but cannot predict the outcome.

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?

Three required parameters with 0% schema description coverage and the description adds nothing. projectId and siteId are self-evident from naming, but idempotencyKey (max 160, min 8) needs an explanation of what duplicate-submission protection it provides, and the description supplies none.

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+resource: 'Scan published articles against search data for new refresh opportunities.' An agent knows the general action is a discovery/scan over published content. However, it does not distinguish itself from close siblings such as generate_article_improvement or get_article_improvements, so an agent cannot tell which of those four improvement tools to pick without opening schemas.

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?

The sentence implies a discovery use case but gives no explicit when-to-use, no prerequisites, and no alternative to prefer (e.g. 'use generate_article_improvement once you have the scan results'). With a dense sibling cluster of *_article_improvement tools, this is a real gap.

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