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

Goes well beyond the annotations: it discloses the rate limit (5 times/day per link), the ownership constraint ('only the passport that made it'), and the side-effect boundary ('the link and the picks stay'). That last point usefully qualifies destructiveHint=true — what is destroyed is the previous browser binding, not the link or picks.

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?

Led by the purpose, then the constraint, then the operational rule and limits — good front-loading. One sentence runs long ('This frees it, so it opens in the next browser where they press Open my page; the link and the picks stay'), but nothing is filler.

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 two-parameter mutation with no output schema, the description covers the mechanism, the trigger condition, the delivery instruction, scoping, and rate limits. The only gap is what the call itself returns on success versus on hitting the 5/day cap.

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 both window_id and passport_token are already documented and the baseline is 3. The description adds context but also introduces mild ambiguity by telling the agent to 'send the same pick_url again' while the actual parameter is window_id — an agent could momentarily misread which value to pass.

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 gives a specific verb (reopen) plus the resource (a pick link created by show_shop_to_owner) and explains the mechanism: the link was bound to one browser and is now released. It names the originating sibling tool, so an agent can place it against show_shop_to_owner and close_shop_window without opening schemas.

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?

Explicit when-to-use ('Use it only when your human asks, for example "it says open in another browser"'), a concrete follow-up action (send the same pick_url again, privately, only to the owner), and an exclusion implied by 'only when your human asks'. That is a full routing rule, not an inference.

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