bulk_update_designs

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

No annotations provided, so description bears full burden. Discloses bulk update behavior but omits details on atomicity, idempotency, error handling, rate limits, or reversibility. Minimal beyond obvious semantics.

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, front-loaded with key information, includes an illustrative example. Zero fluff or 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?

Given the tool's complexity (3 background types, textUpdates array, screenIndices, locale) and no output schema, description is too sparse. Does not explain full parameter behavior or return value. Incomplete for reliable agent invocation.

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 40%; description adds value by naming background and text updates with an example. However, it does not explain the complex structure of background (solid/gradient/image) or textUpdates array. screenIndices and locale are not mentioned, leaving gaps.

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 uses specific verb 'Apply' and identifies resource 'background and/or text updates' across multiple or all screens. Example clarifies the intended use. Distinguishes from sibling single-screen tools like update_screen_design and update_screen_text by emphasizing bulk operation.

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?

Description implies use when needing uniform background/text across screens, but lacks explicit guidance on when to use vs alternatives (e.g., single-screen updates). No prerequisites or exclusions stated.

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