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

Annotations already mark the operation read-only, idempotent, and non-destructive, so the description adds relevant context over and above that: bounded pagination and the explicit exclusion of records, appointments, patient data, and clinical content. This gives a safety/privacy boundary beyond the annotations.

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 short sentences front-load the action and scope, then list exclusions. Every clause earns its place and there is no repetition of schema or annotation content.

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 a rich output schema and annotations covering safety/idempotency, the description covers the remaining decision points: scope, pagination, and content exclusions. It could be more explicit about default pagination behavior, but nothing essential is missing for selecting and invoking the tool.

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?

The schema already documents clinicId and cursor adequately, and the description's 'bounded pagination' adds some meaning to the limit parameter. It does not, however, describe default limit behavior or how cursor pagination is initiated beyond what the schema says, so the added value is moderate.

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 a concrete resource (administrative room names), a specific scope (one tenant-owned DoctoFam clinic), and a mode (bounded pagination). It also states clear exclusions, which distinguishes it from sibling list tools such as list_clinics and list_providers.

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 description clearly sets the context: use this when you need administrative room names for a single clinic. It does not name an alternative tool like some sibling definitions do, but the exclusion of patient/appointment/clinical content gives an agent enough boundary to select it.

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