Update Article Section

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

Describes the fetch-replace-PUT process, preservation of section heading, and potential artifacts with markdown. Annotations already indicate mutating/destructive, so the description adds valuable behavioral context 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?

Four sentences, each serving a clear purpose: purpose, process, format guidance, heading preservation. No redundant information, well-structured and front-loaded.

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?

Covers core behavior and format choices well, but lacks explanation of return value/output (no output schema). Missing details on error conditions or permissions. Adequate but incomplete for a complex tool.

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 covers all parameters (100%), and the description adds specific guidance: notes that heading is preserved and not part of content, and explains format trade-offs. This goes beyond schema descriptions.

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?

Clearly states verb 'replace' and resource 'content of a single section of an article in a given locale'. Distinguishes from siblings like update_article and update_article_translation by specifying single section replacement while keeping rest intact.

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 clear guidance on when to use format='html' vs 'markdown', but does not explicitly contrast this tool with alternative tools (e.g., update_article, update_article_translation). Implied usage context is present but lacks direct comparison.

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