List a brand's official stores

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

With no annotations, the description carries the full burden, and it does add real context: the result set is 'every' store Dropify tracks, includes free/paid status, and the URL is only present 'when Dropify exposes one' — useful nullability information. However, it omits behavior for an unrecognized brand (empty list vs. error), whether matching is exact or fuzzy, and any auth or rate-limit characteristics.

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?

A single front-loaded sentence with no filler: the action, scope, and returned fields all appear immediately. Every clause earns its place by telling the agent what comes back.

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 simple one-parameter read with no output schema, describing the return fields inline is the right call and makes the definition largely self-sufficient. The remaining gap is what happens on an unknown or ambiguous brand name, which the agent cannot infer.

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% for the single 'brand' parameter, including an example value, so the schema does the heavy lifting. The description adds nothing beyond that about name format, normalization, or matching behavior, which is the baseline-3 outcome when coverage is complete.

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 names a specific verb and resource ('List every official store Dropify tracks for a brand') and even enumerates the returned fields (region, free status, URL). It is unambiguous what the tool does, though it never contrasts itself with siblings like find_brand, which an agent could plausibly confuse for a brand-store lookup.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of when to prefer find_brand or restock_alert_link instead. The only implicit signal is that a brand name is required, leaving the agent to infer the tool's role from its name.

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