List booking pages

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the concrete return shape (id, title, subdomain) but says nothing about pagination, result limits, or ordering for what could be a multi-page account, which is the main behavioral gap.

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, all earning their place: identity of the resource, the vocabulary caveat, the return contents, and the downstream use. The most useful routing hint (subdomain for find_available_times) is placed last as a natural call-to-action.

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 no output schema, the description carries the burden of describing return values and does so explicitly, and it flags the profiles/booking-pages naming alias that would otherwise confuse an agent. It is only slightly incomplete regarding pagination behavior and the overridable 'fields' parameter.

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% and the single optional 'fields' parameter is fully documented there, so the baseline of 3 applies. The description does not mention the fields parameter at all, and its field list ('id, title and subdomain') is narrower than the schema's stated default set including description, adding no real semantic value.

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 ('List the account's booking pages') and disambiguates the API's own vocabulary by noting the API calls them profiles. It also enumerates the returned fields, so it is clearly distinguishable from the singular sibling get_booking_page.

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 supplies a concrete downstream reason to call it: 'The subdomain is what find_available_times needs,' which effectively routes the agent from this tool into the scheduling flow. It does not explicitly state when to prefer get_booking_page or search_bookings over this list call, so it stops short of full when/when-not guidance.

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