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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write nature is partly covered. However, the description omits the key behavioral fact that this overwrites existing field content (the very thing an agent needs before calling an AI rewrite), and says nothing about required idempotency, cost, latency, or whether results are staged for review. No contradiction, but thin disclosure for a 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 short sentence, front-loaded with the verb and resource, with zero filler. It is concise but under-specified rather than economical.

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?

With five required parameters at 0% description coverage, no output schema, and a non-trivial AI mutation that overwrites content, the one-line description leaves an agent without enough to call it correctly or predict the result.

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% across five required parameters. The phrase 'chosen fields' gestures at the `fields` array but never explains the enum values (full, title, excerpt, body, meta) or what 'full' implies, and projectId, siteId, assetId, and idempotencyKey are entirely unexplained in both schema and description.

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?

The description names a specific verb (rewrite) and resource (chosen fields of an article) plus the mechanism (with AI), which cleanly separates it from generate_article (full creation) and update_article (manual edit). It stops short of naming those siblings explicitly, so an agent must infer the boundary.

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 statement of when to use this versus generate_article, update_article, apply_article_improvement, or regenerate_distribution_post, and no prerequisites or exclusions. The agent gets a purpose but no routing guidance in a tool list crowded with article-mutation siblings.

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