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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds genuinely useful context beyond them: the result is bounded to the next 14 days and 100 slots, covers only 'unassigned online-booking' slots, and explicitly excludes pet, owner and medical data.

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?

Three tight sentences, front-loaded with the trigger condition, then output shape, then the bounds and exclusion. Every sentence earns its place, though the second sentence slightly restates the first's output framing.

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 not be explained, yet the description still summarizes the payload (per-day counts plus first start/last end). Scope, limits, and the negative boundary are all covered – nothing needed to call this correctly is missing.

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% for the single clinicId parameter, including its pattern, so the schema does the heavy lifting and baseline 3 applies. The description adds no further semantics about the identifier beyond what the schema states.

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 (summarize) and resource (unassigned online-booking capacity for one clinic) with the precise output shape (daily slot counts, first/last slot times). This is distinguishable from siblings like get_clinic_schedule_summary and show_clinic_overview, which the agent can tell apart without opening schemas.

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?

Opens with an explicit trigger condition ('when the user wants to summarize unassigned online-booking capacity') and closes with a clear exclusion ('Not for booking an appointment'). It does not name the specific sibling tool to use instead for booking or for schedule details, so it stops short of the full when/when-not/alternative set.

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