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

The readOnlyHint annotation already signals safety, but the description adds meaningful behavioral context: the tool cannot change availability, and the agent should instead tell the owner what to change and where. This goes beyond the annotation and prevents misuse.

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?

The description is compact and front-loaded with the core purpose, followed by a useful field inventory and a clear behavioral directive. Every element earns its place; there is no filler.

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 field list provides a strong expectation of return contents. The single parameter is fully covered by the schema plus provenance, and the read-only guidance fills the behavioral gap. Nothing essential is missing for an agent to select and invoke this tool correctly.

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% for the single pageId parameter, so the description doesn't need to explain the parameter itself. However, it adds value by specifying where the pageId comes from ('from get_project or list_booking_pages'), which helps the agent obtain a valid 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?

The description states a specific verb ('Read') and resource ('one booking page in full') and lists the exact contents returned. It clearly differentiates this from sibling list_booking_pages by emphasizing full detail for one 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?

The description clearly conveys this is the tool to use when a complete booking page snapshot is needed, and explicitly instructs the agent not to attempt edits. It doesn't name an alternative sibling for comparison, but the 'one page in full' wording implies when list_booking_pages would be more appropriate.

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