set_card_project_qrcode

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

The description adds the useful upsert behavior 'Place (or update)', which clarifies that this tool can modify an existing QR code rather than only create one. The annotations only state destructiveHint=false, so there is no contradiction, but the description does not disclose further side effects or what happens to an existing QR code.

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 with no filler. The action and target are front-loaded, and the crucial cross-tool lookup instruction is placed second. Every sentence earns its place.

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?

With 7 parameters but a fully documented schema, the description covers the main contextual gap: where page_uuid comes from. It is sufficient for a confident call. It could be slightly more complete by mentioning what happens to an existing QR or how to preview the result, but these are not critical.

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%, so the baseline is 3. The description adds important meaning by explaining that page_uuid comes from get_card_project's customization pages array, which is not stated in the schema and is a key source of confusion for callers.

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 action ('Place (or update)'), the object ('a QR code'), and the target ('a specific page of an invitation project'). This makes the tool's responsibility obvious and distinguishes it from page-level tools like update_page or preview_qrcode.

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 gives a concrete prerequisite: the page UUID comes from get_card_project, under the customization's pages array. This is clear contextual guidance, but it does not explicitly mention when not to use this tool or name alternative tools such as preview_qrcode.

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