Get a brand's restock alert link

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

No annotations exist, so the description carries the disclosure burden. It does tell the agent what comes back (a page URL plus a one-line how-to), which is useful return context, and the read-only nature is implicit in 'Get'. It omits error behavior for an unresolvable brand and whether the returned how-to is meant to be relayed to the user verbatim.

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?

One sentence, front-loaded with the primary artifact (the alert page) before the secondary add-on (the how-to). No filler, no restatement of the tool name.

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 one-parameter read lookup with full schema coverage and no output schema, the description covers purpose and return shape adequately. The only gap is failure/unmatched-brand behavior, which is minor at this complexity.

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?

Single parameter with 100% schema description coverage ('Artist or brand name, e.g. bts'), so the schema already does the work. The description adds only that the parameter scopes the page to a brand, which is no more than the schema states — baseline 3.

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: retrieves the Dropify page where restock/drop alerts are set, plus a short how-to. That is clearly distinct from a brand lookup (find_brand) or store listing (official_stores) in both artifact and intent. It only stops short of naming those siblings explicitly.

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?

Usage is implied by the resource itself — call this when a user needs the alert-signup destination for a brand — but there is no explicit when-to-use, no exclusion such as 'use find_brand first to resolve the name,' and no note on behavior for unknown brands. Relying on the agent to infer the routing against two siblings.

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