Update Article Translation

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

Discloses that the tool 'replaces the FULL body and re-sends the entire article on each write', which adds behavioral detail beyond annotations. No contradiction with 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?

Three sentences, front-loaded with main action, then usage guidelines. Every sentence provides essential information without unnecessary words.

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?

Missing return value description and error conditions, but provides solid context for operation choice and behavior. Acceptable for a write tool with annotations.

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?

Despite 0% schema coverage, description explains locale usage well and mentions title/body as updatable fields. However, it does not clarify article_id or draft parameter semantics, so incomplete but helpful.

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 states 'Update article content (title, body) in a specific locale' with a clear verb and resource. It distinguishes from sibling 'update_article_section' by noting this tool replaces the full body.

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?

Explicitly advises when to use the sibling tool for targeted edits and how to choose locale (source_locale vs other). Provides clear context for alternative and correct parameter usage.

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