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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that staff include clinicians and admin and that ids are reused downstream, but says nothing about search behavior, pagination, or the include_deleted effect — context that would help an agent call it correctly.

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 compact sentences, resource definition front-loaded ahead of the workflow hint. Little waste, though the second sentence is more of a usage note than a purpose statement.

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 read-only list tool with full annotation safety coverage and 100% schema coverage, the definition is adequate. The enumerated return fields partly compensate for the absence of an output schema, leaving only minor gaps like pagination/total-count behavior.

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 five parameters (page, search, page_size, clinicians_only, include_deleted) are fully documented in the schema. The description adds no parameter meaning beyond that, making the baseline 3 correct.

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 identifies a specific resource — staff users of the practice (clinicians and admin) — and enumerates the fields returned, which distinguishes it from patient-facing siblings like semble_list_patients. It lacks an explicit list verb, leaning on the tool name, but the scope is 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?

'Use the ids for bookings and tasks' gives a downstream workflow hint, implying this is the lookup step before create_task/list_bookings. However, it never states when to prefer this over semble_get_user or other list tools, so usage is only implied rather than spelled out.

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