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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds value beyond that by listing the returned field set (id, name, email, NPI, credentials, roles) and the underlying API source, which matters because no output schema exists.

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?

One dense sentence that front-loads the resource and return fields, with the cross-tool usage hint last. The trailing 'Photon GraphQL (clinical API): users' tag is a minor source annotation that borders on noise but costs little.

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 usefully compensates by naming the returned fields, and pagination/filter params are fully covered by the schema. It is nearly complete; only deeper filtering behavior (e.g., substring vs exact name match) is left unstated.

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 coverage is 100% and all three params (name filter, page_num, page_size) are documented in the schema, so the baseline is 3. The description's mention of 'id' refers to an output field, not an input parameter, and adds no syntax or semantics for the inputs.

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 and resource ('List the organization's users') and disambiguates from siblings by scoping to 'prescribers and staff', which separates it from list_patients. It also enumerates the returned fields, so an agent knows exactly what this tool yields.

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?

Gives a concrete downstream use case: 'use an id as prescriber_id in list_prescriptions', which explains why an agent would call this before writing a prescription. It lacks explicit when-not guidance or a named alternative, but the context is clear.

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