lokalise_bulk_update_keys

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

No annotations provided, so description carries the burden. It discloses performance (up to 1000 keys), required fields, and return format (updated keys and errors), but does not detail side effects like partial failures or atomicity.

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 tight sentences: purpose, usage/requirements, and return/performance. Every sentence adds value, front-loaded, no fluff.

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?

Without an output schema, the description adequately covers return info. With two parameters and clear usage guidance, it is mostly complete. Minor gap: no mention of field-level partial updates behavior.

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 coverage is 100% with descriptions for all parameters. Description restates the required format minimally, adding no new semantics beyond the schema, so baseline 3 is appropriate.

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 'modifies metadata for multiple keys in one operation', specifying the verb and resource, and distinguishes from sibling tools like 'lokalise_update_key' (single key) and 'lokalise_bulk_delete_keys' (delete).

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 use cases ('large-scale reorganization, batch platform updates, or systematic tagging') and efficiency guidance ('more efficient than individual updates for 3+ keys'), but does not explicitly name the alternative tool for single updates.

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