Free appointment slots

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, but the description adds real value by clarifying it 'does not hold or book one' and that actual booking requires an SMS login outside this tool. It does not cover rate limits or pagination, so it falls short of a 5 given annotations carry the safety profile.

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?

Front-loaded with the core purpose, then a compact paragraph covering read-only behavior, ID sourcing, and the booking path. Every sentence earns its place; slightly long but no waste.

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, return fields needn't be explained, and the description still proactively mentions next_free_day behavior plus the booking hand-off. Complete enough for correct invocation, though it omits the 14-day range cap that lives in the schema.

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 all five parameters are documented in the schema, including the 14-day cap and ID formats. The description adds only the 'Tehran HH:MM' time convention and date-range scoping, which is marginal beyond the schema — 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+resource ('Free appointment start times ... per day for one service of a doctor at one center, for a date range'), including the scope dimensions that matter. It is clearly distinguishable from the sibling pz_free_days (day-level) versus this tool (slot-level).

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 routes the agent: get ids from pz_doctor or a search card, find days with pz_free_days, and send the user to the profile URL to book. It also states the edge case behavior (no free slot → next_free_day) so the agent knows how to interpret an empty result.

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