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

readOnlyHint=true already tells the agent this is a safe read, so the burden is lighter. The description adds the underlying endpoint (GET /v3/user) and the role composition of the result, but says nothing about default page size, whether the full roster is returned in one call, or result ordering.

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 sentence plus an endpoint tag, front-loaded with the verb and resource. No filler, no restatement of the title, and the most decision-relevant detail (the ids are for technicians/service writers) sits before the endpoint reference.

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 read-only list tool with full parameter documentation and a readOnly annotation, this covers what an agent needs to decide and call. The only gap is return-shape detail — it hints that ids are the payload but doesn't say what else each user record contains, and there is no output schema to fall back on.

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% and both parameters (skip, limit) are documented in the schema with ranges and usage notes, so the description need not repeat them. It adds no paging semantics beyond the schema, so the baseline 3 applies.

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+resource ('List the shop's users') and enumerates the roles returned (service writers, technicians, admins), which tells an agent exactly what domain object comes back. It also distinguishes itself from shopmonkey_get_current_user by scoping to the whole shop rather than the caller.

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?

The clause 'the ids to use for technicians and service writers' makes the downstream usage explicit — an agent knows to call this before setting technician/service-writer fields elsewhere. There is no when-not guidance or named alternative, but the context is unambiguous.

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