Doctor profile

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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower; the description nonetheless adds real behavioral context: what 'booking_off: true' means (call the phone), what 'booking_opens' means (slots open later), and that booking happens externally with SMS login. No contradictions.

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?

Purpose and payload are front-loaded in the first sentence, and the guidance sentences are short. However, the long parenthetical field enumeration and mid-sentence line breaks ('...pz_resolve_url. The center_id + user_center_id + service_id of a service feed...') add some density without much extra value.

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 an output schema present, the description need not explain return values, yet it does summarize them. It covers the mutation-free nature and downstream id chaining, leaving only minor ambiguity about how the returned center/service ids are meant to be threaded into the listed sibling tools.

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?

Only one parameter with 100% schema description coverage, including an example and the note that it accepts either a slug or a profile URL. The description adds no syntax or format detail beyond the schema, so 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 and resource ('Full profile of one doctor') and enumerates the exact payload: specialties, council code, ratings, insurance, online visit channels/price, and every office with address, phone, map, first free slot and services. It is immediately distinguishable from list/search siblings like pz_search_doctors or pz_center.

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?

Explicitly says to use it 'after pz_search_doctors or pz_resolve_url' and explains the booking flow ('Booking itself is done by the user on the returned url (it needs an SMS login)'). No explicit when-not-to-use condition is given, but the placement in the tool chain is clear.

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