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

Annotations already declare the mutation profile (readOnly=false, idempotent=true, destructive=true); the description adds a scope guarantee beyond them — 'Only the status (and optionally the article it produced) is changed' — and discloses a side effect that is not in annotations, namely that `dismissed` suppresses the idea from future suggestions. It does not explain the destructive aspect flagged by the annotation (e.g. whether clearing the article link is what makes it destructive).

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 core action and its three states are front-loaded before the scope-limiting caveat. Every clause carries information the agent needs.

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 an output schema present, return values need not be described. All three parameters are schema-documented, the mutation semantics are partly covered by annotations, and the description fills the remaining gaps (state meanings, side effect on suggestions, blast radius), so an agent has everything required to call it correctly.

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 already 100%, so the baseline is 3. The description still adds meaning over the raw schema by defining what each enum value means operationally and by confirming that usedForArticleId is only meaningful alongside `used`, which helps an agent avoid a meaningless combination.

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 concrete verb (move/set the lifecycle status) and a concrete resource (a saved topic idea), and enumerates the three target states. That vocabulary is specific enough to separate it from the read-only siblings list_topic_ideas and refresh_topic_ideas without opening a 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?

It gives explicit when-to-use conditions for each value: `used` once an article has been written, `dismissed` to keep the idea out of future suggestions, `new` to reset. It does not, however, point to alternative tools such as list_topic_ideas or refresh_topic_ideas for the cases where this tool is the wrong choice.

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