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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description usefully adds that it "opens nothing by itself" and that it returns procedural output (screens, buttons, fields), but the API note about no self-serve key is tangential and adds little operational value for invoking the tool.

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 operative content (what it returns, that it does nothing itself, and the browser follow-up) is present, but the trailing sentence about the ProSolutions API host is rambling boilerplate that does not help an agent decide or invoke. The middle clause chain is dense and could be front-loaded more sharply.

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, read-only tool with no output schema, the description covers what it returns and the next step, which is most of what is needed. However, the tension between the tool name ("lookup hotel guest") and the stated behavior (returns how-to instructions only) is unresolved, and no return-shape detail is given to compensate for the missing output schema.

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 zero parameters and schema coverage is 100%, so there is no parameter meaning the description needs to supply. Baseline 4 applies for a parameterless tool.

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+resource ("Lookup hotel guest in the user's own Paired Plus account") and clarifies it returns step-by-step procedure text rather than performing the lookup itself, which separates it from the action tools. The name implies retrieving guest data while the description says it only returns instructions, which leaves the core output slightly ambiguous.

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?

Gives a follow-up path ("then do it with the cotlet_browser_* tools in the user's Paired Plus Cloud Browser"), which implies this is a preparatory step. It does not state when to prefer this over sibling action tools or what happens if the user wants the lookup done directly, leaving selection guidance implicit.

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