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

Annotations already declare read-only/non-destructive/open-world=false, so safety is covered; the description adds real domain behavior beyond that: the 7-day hold for class bookings and 1:1 requests at non-gym-plan places, expiry timing, accept-now eligibility, and the auth prerequisite (connected Phorme account that owns the place).

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 use-case trigger in the first sentence, followed by policy, payload, safety, and auth in a compact block. Every sentence carries information, though the return-field enumeration is somewhat list-heavy given an output schema exists.

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, the description need not detail return values, and it still supplies the business rule (7-day hold), auth requirement, and safety profile an agent needs. The only gap is that it never echoes the place_id default behavior, which the schema already covers.

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% on the single place_id parameter and its 'leave out for all places' semantics, so the baseline is 3. The description alludes to 'the place' and non-gym-plan places but adds no parameter-level syntax or default information beyond the schema.

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 in owner-facing terms ('list asks waiting for my gym' / 'who wants to book or visit their place'), so an agent can tell it is the read-side counterpart to answer_held_request. The example query (

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 an explicit trigger condition (an owner asks who wants to book or visit) plus a natural-language example phrasing. It does not name the sibling action tool (answer_held_request) or state an exclusion, so it stops short of a 5.

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