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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's main contribution is the disclosure that the refreshed content replaces the public version and that a recoverable snapshot is stored first – genuinely useful mutation context. It stops short of stating that the rewrite is asynchronous or that repeated invocations (idempotentHint=false) produce separate rewrites, which would have completed the picture.

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, zero filler, and the most important fact for an agent – that this mutates public content – is front-loaded. Nothing would be lost by keeping it exactly as is.

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?

An output schema exists and annotations cover the safety profile, so the description only needs to add the replacement semantics and locale scoping, which it does. The remaining gap is the asynchronous/trigger nature of the operation and whether a job handle is returned, which an agent would want before calling.

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 100% for the single article_id parameter, so the schema already carries the meaning. The description adds no format, range, or constraint details beyond what the schema states, so the baseline of 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?

"Trigger a rewrite of a published article in the tenant's default locale" gives a specific verb (trigger rewrite), resource (published article), and scope (tenant default locale). It is distinguishable from trigger_generation and publish_article by implication, but it never names those siblings, so the differentiation is inferential rather than explicit.

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 phrase "published article" implies the precondition that the article already exists and is live, but there is no explicit when-to-use guidance, no statement of when to prefer trigger_generation or publish_article instead, and no exclusions. Usage must be inferred from the sibling list.

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