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

Annotations declare the safety profile (not read-only, not idempotent, not destructive), and the description adds two useful facts beyond them: it is slow, and it returns added/updated counts. That latency and return-shape context is genuinely helpful since there is no output schema. It omits auth/permission requirements, keeping it short of a 5.

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?

Two tight sentences with zero waste; the core action is front-loaded and the cost/return caveats follow immediately.

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 sync tool with annotations covering safety and no output schema, the description covers action, latency, and return shape adequately. It leaves minor gaps around prerequisites and the all-locations vs single-site discrepancy.

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 the single 'site' parameter is already fully documented, establishing a baseline of 3. The description adds nothing about the parameter and in fact says 'every connected location' while the schema requires one specific site, a mild tension an agent may need to resolve.

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 gives a specific verb and resource ('Re-reads every connected Dutchie location's menu into the product catalogue'), so the scope is clear. It does not explicitly distinguish itself from the sibling sync_products, but the Dutchie qualification makes the intent reasonably unambiguous.

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 guidance on when to call this versus sync_products, or whether get_dutchie_status / get_product_sync_status should be checked first. The word 'Slow' hints at a cost but does not translate into a usage rule.

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