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

Beyond the readOnly/idempotent annotations, the description discloses a critical behavioral trait: this connection lacks the required Floreal Workspace sign-in, and the tool responds with what is wrong and how to fix it. This tells the agent exactly what kind of response to expect and why the tool is still useful.

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 three compact sentences with no filler. The most important fact, the sign-in requirement, is front-loaded, and the call behavior is stated directly.

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 tool with comprehensive annotations and no output schema, the description covers what the tool does when signed in, what it returns, and what happens without the workspace sign-in. An agent has enough context to invoke it correctly and set user expectations.

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 schema coverage is 100%, so the description has no parameter burden. Baseline 4 applies because with no parameters the description needs to compensate for nothing.

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 says the tool returns one reservation with dates, party size, room, and status, which is a specific verb+resource. It does not explicitly differentiate from sibling search tools like bookings_search or search_stays, but the singular 'one reservation' makes the scope clear enough.

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 clearly states when to call the tool: 'Call it anyway when the user asks for this,' and explains the sign-in limitation that the agent should expect. It doesn't mention when not to use it or name alternative tools, so it stops short of the full 5.

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