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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing the result state machine (live/claimed, waiting, gone) and that an embed code is returned, which is not derivable from the annotations or the input schema. It stops short of explaining what distinguishes 'gone' from 'waiting' operationally.

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?

A single front-loaded sentence with zero filler; the primary outcome set comes first and the embed-code return is appended as a secondary clause. Nothing could be removed without losing information.

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 one-parameter, read-only tool with no output schema, the description covers both the possible statuses and the returned embed code, which is what an agent needs to interpret the response. The only gap is that failure behavior for an invalid or unknown setup key is not addressed.

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 schema itself explains the 'setup' key format (stp_…). The description only echoes the origin of that key ('returned when the page was made') and adds no new syntax, validation, or error-handling detail, so the schema does the heavy lifting.

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 ('Reports whether a booking page is...') and enumerates the three possible outcomes (live/claimed, waiting, gone) plus a secondary return (embed code). It does not name or contrast with the sibling set_up_booking_page, so an agent must infer that this is the read-side counterpart to page creation.

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: an agent can reasonably infer this is a post-creation status check, since the description says the setup key is 'returned when the page was made'. There is no explicit statement of when to call this versus set_up_booking_page, and no mention of what to do if the status is 'gone'.

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