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

Annotations already cover write status, non-destructiveness, and non-idempotency. The description adds meaningful behavioral context beyond that: the API key is stored write-only and never returned, and the first menu pull is slow. It does not mention failure modes or permission requirements, but the added security and performance details make it genuinely helpful.

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 compact sentences are front-loaded with the core action, then security behavior, then a latency caveat. Every sentence carries distinct, useful information without repetition or filler.

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 write-connect tool with no output schema, the description covers purpose, key handling, and performance well, while annotations already declare the safety profile. It leaves out failure behavior and whether an existing connection is replaced, but it is otherwise complete enough to call 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 three parameters are already documented in the schema. The description does not add syntax or meaning beyond what the schema provides for site, label, or apiKey, which is acceptable at this coverage level but not enriching.

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 the specific action (verifies a Dutchie API key, attaches its store location, pulls the live menu) and the resource (Dutchie location). It distinguishes this tool from related siblings like sync_dutchie and get_dutchie_status through the initial-connect wording, but it does not explicitly name or compare those alternatives.

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 alternative sibling tools are named. The latency note '(first menu pull)' is a useful caveat but not a usage guideline. An agent must infer from the name that this is for initial setup rather than ongoing syncing.

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