Update Help Center Article

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

Annotations already indicate this is a write (readOnlyHint=false) and destructive (destructiveHint=true). The description adds behavioral clarity by limiting scope to metadata only and providing detailed positioning behavior, which goes beyond annotations.

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 with zero redundancy. First sentence states purpose and examples, second sentence clarifies exclusion and points to sibling. Information-dense and well organized.

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?

Given 10 parameters and no output schema, the description covers the core functionality and constraints. It explains what is and isn't updated, and provides a usage example for position. It could mention partial update behavior but is generally sufficient.

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?

Description lists parameter categories (draft, promoted, labels, etc.), adding context beyond the schema which has 60% coverage. The position parameter gets an extensive explanation of usage, which is highly valuable. However, not all individual parameters are described in detail.

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?

Description clearly states it updates article metadata only, with a list of example fields. It explicitly excludes content updates and directs to the sibling tool update_article_translation, making purpose very specific and distinguishable.

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?

Provides explicit when-to-use (metadata updates) and when-not-to (content updates), naming the alternative tool. Could be more comprehensive about other siblings but is strong on the key distinction.

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