update_app_store_qr

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

The description adds behavioral context by noting 'Partial updates merge with existing data', which is useful. However, without annotations, it lacks transparency on permissions, idempotency, side effects, or error conditions.

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?

The description is concise (two sentences) with the purpose front-loaded, followed by a key behavioral detail. No extraneous information.

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?

For a tool with moderate complexity (5 params, no output schema), the description is mostly complete. It explains the update and partial merge. Could mention return value or default behavior, but overall 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?

The input schema has 100% description coverage, so the schema already documents parameters. The description adds value by explaining the merge behavior, which clarifies that omitted fields are not cleared. This exceeds the baseline of 3.

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 clearly states the verb 'Update' and the resource 'App Store QR code', specifying that it updates app store URLs. It distinguishes itself from siblings like 'create_app_store_qr' by implying an existing code and from 'update_qr_destination' by targeting a specific QR type.

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?

The description implies usage when modifying an existing App Store QR's URLs but does not explicitly state when to use this tool over alternatives like 'update_qr_destination' or other update tools. No exclusions or sibling references are provided.

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