Get the booking page

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to restate safety. It adds value by specifying the authenticated-user scope and the exact fields returned, which helps the agent anticipate the response. It goes beyond the structured annotations without contradicting them.

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 a single efficient sentence that front-loads the resource and then provides a compact list of relevant response contents. There is no filler, repetition, or redundant explanation.

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 no-parameter, read-only getter with an output schema and strong annotations, the description is complete. It conveys what the tool returns and for whom, while the output schema can carry the detailed return structure. Nothing essential is missing.

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 has zero parameters, and the schema description coverage is 100%, so there is nothing for the description to add about parameter semantics. The baseline for zero-parameter tools is 4, and the description appropriately says nothing about inputs.

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 names a specific resource, 'the authenticated user's personal booking page,' and enumerates its concrete contents: colours, header image, description, profile links, and meeting-type order. Together with the verb in the title ('Get'), this is unambiguous and distinct from related tools like get_me or list_meeting_types.

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 implies usage: retrieve the current user's booking page configuration. However, it does not explicitly state when to prefer this tool over alternatives such as get_me or list_meeting_types, nor does it mention exclusions or edge cases. It offers clear context but no explicit routing guidance.

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