list_doctors

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description's job is lighter. It adds useful behavioral context by specifying the return fields (id, name, specialty, clinic address) and the optional filtering behavior, though it does not mention pagination or result limits.

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?

The description is one sentence and conveys the core behavior, the optional filter, and the returned data in an efficient, front-loaded way. There is no wasted text or redundancy.

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 operation, this description is complete: it states what is listed, how it can be filtered, and what fields are returned. The annotations cover safety and idempotency, and there are no nested objects or complex outputs requiring additional explanation.

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 provides 100% coverage for the single optional 'specialty' parameter, including that it must be an exact specialty name from list_specialties. The description reinforces the optional narrowing concept but does not add significant meaning beyond the schema.

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 uses a specific verb ('List') and names the resource (doctors), while also noting the optional narrowing by specialty. This clearly distinguishes it from sibling tools list_specialties and list_my_appointments, which target different resources.

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 states that the tool can be narrowed by specialty and the schema parameter notes the exact specialty should come from list_specialties. It does not explicitly discuss when not to use this tool, but the read-only listing context and sibling names make the intended use clear.

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