Update base-language copy (local draft)

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

Describes upsert behavior, local-only impact, and character-limit constraint. With no annotations, it covers essential safety but omits error cases, response format, and prerequisite checks beyond character limits.

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 pack key information: action, scope, constraints, and a parameter hint. No redundancy.

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 usage, but lacks return value description. Given tool simplicity and no output schema, it is mostly adequate.

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?

Adds context for iapProductId ('set an IAP display name') and implies fieldType selects the field. With 60% schema coverage, description enhances understanding but doesn't explain all parameters 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?

The description uses a specific verb ('Upsert') and resource ('base-language text of one metadata field in ShipLocale's local draft'), clearly distinguishing it from live listing updates and sibling tools like update_localization.

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 states local-draft-only scope and to respect character limits. Mentions iapProductId for IAP display names. Lacks direct comparison to sibling tools but context is clear.

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