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

Annotations already cover readOnly/idempotent/non-destructive, so the description's job is to add context beyond that — and it does, disclosing the auth requirement and describing the returned shape including the snip.link/c/<address> URL form and that a public page only appears when enabled.

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?

Front-loaded with the resource and its payload, then the auth prerequisite, then the alternative — a logical order with no filler. The parenthetical '(snip.link/c/<address>, one button per live link)' is dense but earns its place by describing return values that no output schema documents.

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 no output schema, the description carries the return-shape burden and does so reasonably, covering link counts and public page URLs. It leaves minor gaps — ordering, whether empty collections are included — but nothing that would cause a wrong invocation.

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?

The tool takes zero parameters, so per the baseline this scores 4. The description correctly implies scope via 'the user's collections' rather than suggesting any filtering input exists.

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 resource — the user's Snip.link collections — and defines what a collection is (links grouped by hand) plus what each entry carries (link count, public page). This clearly separates it from list_links and list_domains, which enumerate different resources.

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?

Names save_collection as the sibling to use for modification, implicitly framing this tool as the read path, and states the prerequisite that the user must be signed in to Snip.link. It stops short of an explicit 'use this when you need X instead of list_links' routing statement.

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