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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description still adds genuine value by disclosing the security-relevant behavior that API keys are never returned, only hasKey, plus the return contents. "Read only" merely restates readOnlyHint, which is why this isn't 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?

A single dense, front-loaded sentence with no filler; the trailing "Read only" is the only mildly redundant phrase given the readOnlyHint annotation.

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 burden of describing return content, and it does so completely: connection state, locations, hasKey instead of keys, sync timestamps, and recent errors. An agent knows what it will get and that it is a safe read.

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?

Only one parameter (site) with 100% schema coverage and an enumerated value, so the schema already carries full meaning. The description adds nothing about the site parameter, making the baseline 3 appropriate.

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 resource (Dutchie connection status) and enumerates exactly what is returned: connection state, connected locations, last/next sync, and recent sync errors. That content scope implicitly separates it from siblings like connect_dutchie, sync_dutchie, and remove_dutchie_location, though it never names an alternative 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?

"For dispensaries" scopes the audience, and a status tool's usage is reasonably inferable (checking connection health before syncing), but there is no explicit when-to-use guidance or routing against connect_dutchie/sync_dutchie.

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