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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds real behavioral context on top: which capabilities are blocked until confirmation (appointment emails/texts, directory listing, search indexing, invites, API keys) and the lifecycle consequence that unconfirmed agent-created accounts are deleted at deletesAt. That kind of consequence disclosure is exactly what annotations cannot convey.

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, front-loaded with the core answer (confirmation status) and using a compact parenthetical list for the gated features. Slightly dense and the trailing booking-page-URL sentence reads as an add-on, but nothing is wasted.

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?

There is no output schema, so the description carries the return-value burden and does so by enumerating the statuses and gated features it reports. It stops short of describing the actual response shape or field names, and does not explain why booking page URLs surface here rather than from get_booking_page.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter syntax to explain. The description correctly implies the account is resolved from context rather than an argument.

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 states precisely what the tool reports: email confirmation state, the features gated on confirmation, deletion timing, and location booking page URLs. It is a specific resource-status report rather than a tautology, but it never distinguishes itself from lookalike siblings such as get_booking_page or get_location_setup, so an agent must infer the boundary. The appended "Also lists each location's booking page URL" clause slightly blurs the single purpose.

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?

Usage is only implied: the note about agent-created unconfirmed accounts being deleted at deletesAt suggests checking status after provisioning. It never says when to call this versus verify_email, resend_verification_email, or get_booking_page, which are the obvious adjacent actions. Adequate but leaves routing to inference.

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