Pool Pro Florida

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

Annotations already declare it is a non-destructive write in an open world; the description adds the key side effect that a successful booking fires the existing Cal.com webhook and creates the lead in Pool Founder. That downstream consequence is not derivable from annotations or schema. It omits idempotency behavior and what happens on failure or double-booking.

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: purpose first, then prerequisites/required inputs, then the downstream effect. No filler and no repetition that isn't load-bearing for invocation.

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?

For a write tool with no output schema, the description covers the trigger condition, required inputs, and the resulting lead creation, which is what an agent most needs. It could still say what the tool returns on success (confirmation id, booked time) to close the remaining gap.

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 seven parameters are already documented, including the 'start' constraint. The description repeats the four required fields and the exact-start requirement without adding new syntax, format, or default information beyond the schema (timeZone default, phone formatting, notes are all schema-only). 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 ('Book'), resource ('Pool Pro Florida appointment'), and provider ('through Cal.com'), plus the precondition that the customer has already selected a time. An agent can distinguish this from get_available_times and create_lead without opening any 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 says when to call it ('after the customer has selected an available time') and ties the required 'start' value to the get_available_times output, which is strong context. It stops short of naming create_lead as an alternative or explicitly telling the agent not to call it, though the webhook note implies the lead is created automatically.

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

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

With no annotations, the description carries the full burden and does disclose the key side effect: it writes a lead into Pool Founder, and a duplicate is created if a booking already happened via the webhook. That is a genuinely valuable behavioral hazard. It does not mention permission/auth requirements or what the response contains, so it stops short of a 5.

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 sentences, no filler. The positive scope comes first and the critical 'do not call before book_appointment' warning is front-loaded in the second sentence where it will be read.

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?

For a six-parameter mutation tool with no annotations and no output schema, the description covers purpose, correct sequencing, and the duplicate-lead side effect. It omits return-value expectations and permission needs, but those are minor relative to the sequencing guidance it provides.

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% (all six parameters are documented, including examples for 'service'), so the schema already does the heavy lifting. The description adds no formatting, validation, or optionality guidance beyond it, which is the baseline 3 case.

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?

The description names a specific verb and resource ('Create a Pool Pro Florida service lead in Pool Founder') plus the qualifying condition ('customer is interested in service but is not yet booking an appointment'). That condition alone lets an agent distinguish it from book_appointment without opening either 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?

It gives an explicit prohibition ('Do not call this before book_appointment for the same inquiry') and the underlying reason (the Cal.com booking webhook already creates the lead), which is exactly the routing information an agent needs. The alternative tool is named, so there is no inference required.

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

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the agent knows this is a safe read against an external system. The description adds the 'real Cal.com' qualifier (confirming live external data) but says nothing about return shape, result limits, or empty-result behavior.

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 short sentences, front-loaded with the core purpose. The date-format instruction duplicates the schema pattern, which is a minor redundancy, but nothing is padded.

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?

No output schema exists, so the description should ideally describe what availability comes back (a list of slots, their shape, or how to feed them to book_appointment). That gap leaves the agent guessing about the response, though the input side is fully covered.

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 start, end and timeZone are already documented, and the description's 'Use date-only YYYY-MM-DD values' merely restates the schema pattern. Baseline 3 is appropriate when the schema does all parameter work.

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 ('Get ... appointment availability') scoped to a named business (Pool Pro Florida) and a named source (Cal.com). An agent can immediately distinguish this from book_appointment and create_lead, which are obviously different operations.

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?

'Use this when a customer wants to schedule a pool consultation or service appointment' gives clear triggering context. It stops short of naming the alternative (book_appointment) or stating that this returns options rather than confirming a booking, so the routing is implied rather than explicit.

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