Earliest free appointment

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real context beyond them: results are per center, cover both in-person and online visits, and are in Tehran time, which matters for interpreting slot times.

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 tight sentences, capability stated first, workflow routing second. The parenthetical center hint is slightly tangential for a one-parameter tool but still compact and useful for follow-up calls.

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?

An output schema exists so return values need no prose, and the description supplies the time-zone and scope context needed to interpret results. Combined with 100% schema coverage on the sole parameter, the definition is largely complete.

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 the single slug parameter is fully documented in the schema itself (Persian slug from pz_search_doctors or profile URL). The description adds no slug syntax or formatting beyond that, so this is a baseline 3; its extra center_id '$5532' note pertains to other tools' parameters, not this one's.

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 capability: whether a doctor is bookable now plus the nearest free slot, scoped to in-person/online and per center. It names its sibling relationship (pre-check before pz_free_days / pz_free_slots), so an agent can place it in the toolchain without opening a schema.

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 positions itself as 'a quick check before pz_free_days / pz_free_slots', giving clear ordering relative to alternatives. No when-not or exclusion cases are stated, but the workflow role is unambiguous.

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