Create a link

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

Annotations only declare the mutation/safety profile (readOnlyHint=false, openWorldHint=true), so the description's explanation of what the link does — App Links/Universal Links, store-or-website fallback, destination retained through install — adds genuine context. It omits what happens on a duplicate slug or how failures surface, which matters given idempotentHint=false.

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?

Three sentences, front-loaded with the action and scope, then the return value, then an alternative. The shortUrl host pattern is useful rather than padding; nothing is wasted.

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 13-parameter creation tool with no output schema, the description covers the return value (shortUrl to share) and link behavior adequately. Duplicate-slug behavior and error semantics remain undescribed, but this is a minor gap against a rich schema.

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 92%, so the schema already explains slug, longUrl, expiry, fallback URLs and preview fields in detail. The description adds no parameter-level guidance of its own, which is acceptable at this coverage level.

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 ('Create one deep link (short link)') plus the scope ('in the workspace of STRAIT_SECRET_KEY'), and distinguishes itself from the bulk sibling. An agent can select it without opening the schema.

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?

Explicitly routes bulk work to batch_create_links ('For more than a few links use batch_create_links'), giving a real alternative with a selection condition. No explicit when-not for single creation, but the context is clear.

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