Free appointment days

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

Annotations already declare readOnlyHint/idempotent/destructive=false/openWorld, and the description reinforces this while adding real context: 'nothing is reserved' clarifies the call has no side effect on availability. It also discloses the result's temporal scope (6-8 weeks) and that weekly days off and holidays are included, which the annotations do not cover.

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?

Short and front-loaded: scope of the return value first, then a workflow/safety note. Sentence fragments (e.g. 'Next: pz_free_slots ...') are terse but readable and each clause carries information.

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-format explanation is unnecessary, and the description covers scope, provenance of ids, read-only nature, and next steps. It leaves minor gaps around volume/pagination of returned days, but nothing an agent needs to invoke it correctly.

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 each parameter already carries an example and a source hint. The description only adds provenance ('Get the ids from pz_doctor'), which is mild value over the schema; baseline 3 for high-coverage schemas is appropriate.

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 precise verb+resource: days with at least one free appointment, scoped to one service, one doctor, one center, across the whole booking window. It also distinguishes itself from neighbors by naming pz_doctor as the id source and pz_free_slots as the follow-up for times.

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?

Gives clear context for when to call it (finding candidate days before picking times) and routing: ids from pz_doctor, then pz_free_slots, with booking happening on the doctor's profile URL. No explicit when-not-to-use or named exclusions, which keeps it just below a 5.

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