Create an OtaKit preview link

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

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world behavior. The description goes further by scoping the effect ('private', 'one phone', 'no other device is affected', auto-expiry), which is exactly the kind of blast-radius context annotations cannot convey. It omits whether auth/permissions are required beyond the plugin requirement.

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 dense sentences with the core action front-loaded and the safety scoping at the end. Every clause earns its place, though the first sentence is long and could be split for scannability.

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?

No output schema exists, and the description usefully tells the agent to 'share the returned url' and mentions the QR code, covering the return shape at a high level. Required appId/urlScheme conditions are covered by the schema, so the definition is nearly complete for calling the tool correctly.

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 description coverage is 100%, so all four parameters are already documented (appId optionality, bundleId, expiresIn enum with default, urlScheme). The description only loosely ties to expiresIn via 'until ... the link expires'; it adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: creates a private link and QR code that open an uploaded bundle in the installed app on one phone. The single-phone, temporary scope clearly distinguishes it from siblings like publish_release and revoke_preview.

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?

Gives clear context and prerequisites: plugin 3.2+ with preview links enabled, and the link lives until the tester exits or it expires. It does not explicitly contrast with alternatives such as publish_release, but the described effect ('nothing is released') implicitly rules those out.

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