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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; beyond that the description adds auth requirements (NOMADSTAYS_MCP_AGENT_TOKEN with 'bookings' scope) and return-field behavior (needsAction, ready-to-use checkoutUrl). With no output schema, disclosing those return semantics carries real load.

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, purpose and scope front-loaded, and every clause adds actionable information — output fields, proactive trigger, justification, and auth prerequisite. No filler or repetition of the title.

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 zero-parameter, no-output-schema tool, the description covers scope, ordering, returned fields, the required token and scope, and the expected agent behavior on needsAction bookings. Nothing an agent needs to call and act on this tool correctly 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 takes no parameters, so per the baseline there is nothing the description needs to disambiguate. It correctly adds no parameter prose, keeping the payload clean.

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 gives a specific verb and resource with explicit scope and ordering: bookings owned by the caller's own account, most recent first, with current status. This cleanly separates it from siblings like getMyStays (stays, not bookings) and getBookingStatus (a single booking's status).

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 states exactly when to call it (proactively at the start of a session, or when the member asks what's pending) and why the proactive call matters — there is no other notification path for an incomplete booking over this connection. That is explicit when-to-use guidance plus a rationale, not just implied context.

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