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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety bar is low; the description still adds real context by stating it 'opens nothing by itself' and that the return value is procedural content (screens, buttons, fields) rather than reservation records. The API/partnership note explains the constraint that forces browser automation. It stops short of describing output shape or failure modes.

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 critical behavioral fact – that this returns instructions and performs nothing – is buried in the middle of a long compound sentence rather than front-loaded. The trailing API/partner paragraph ('checked 11 Oct 2026') is relevant justification but reads as an aside and could be tightened into a single clause.

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 what matters: what comes back (step-by-step guidance), what it does not do (no side effects, no data retrieval), and which sibling tools complete the job. It would be stronger if it named what to pass to cotlet_browser_navigate/click and noted that no reservation data is returned directly.

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, so there is no schema surface for the description to compensate for; baseline 4 applies. Nothing in the description adds required input context that is missing.

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 opening sentence claims the tool lists reservations, but the very next clause states it 'Returns how to do it in SiteMinder step by step (screens, buttons, fields) and opens nothing by itself' – i.e. it is a how-to/guide tool, not a data-retrieval tool. The true behavior is eventually stated, but the agent must reconcile a name-and-lead-sentence that says one thing with a body that says another. It is distinguishable from the cotlet_browser_* siblings once read, but the framing is internally conflicted.

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 gives an explicit two-step workflow: call this to get the click path, then 'do it with the cotlet_browser_* tools in the user's SiteMinder Cloud Browser.' It also explains why direct retrieval is not an option (SiteMinder APIs for reservations require a partner agreement and certification). What is missing is an explicit when-not-to-use case or a named alternative for actually returning reservation data.

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