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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add value by naming what the tool returns (a QR code and a link), which matters since there is no output schema. It does not explain whether the link is per-shop, whether the QR encodes the shop_url, or whether the share is ephemeral.

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?

It is short and front-loads the artifact and the trigger phrase, which is good. The trailing sentence 'Name a shop to share it with that café picked' is ungrammatical and does not clearly earn its place, weakening an otherwise tight definition.

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 single optional-parameter, read-only tool with no output schema, the description correctly explains the returned artifact and when to use it. What remains unclear is the effect of shop_url on the generated link/QR and whether that is covered by the default, which an agent would want before passing it.

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 shop_url is already documented as a shop URL from find_shops with a default. The description's only attempt at parameter guidance is the garbled 'Name a shop to share it with', which vaguely gestures at passing a shop but conflicts in wording with the URL-shaped parameter the schema defines. Baseline 3 applies given the high schema coverage.

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 states a specific outcome: it produces a QR code and shareable link that lets others add agentPickup to Claude, ChatGPT or Grok. That is clearly distinct from the order-management siblings (create_pickup_order, pay_order, join_group_order) and from find_shops. The closing phrase 'that café picked' muddies an otherwise clear statement, but the core purpose is unambiguous.

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?

It gives explicit trigger conditions: use when the user asks how to share agentPickup, invite friends, or get others using it. No exclusions are stated, but the sibling set contains no competing sharing/invite tool, so there is little ambiguity to resolve.

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