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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description is consistent with them by saying it 'opens nothing by itself.' It adds real value by describing what the output is (step-by-step screens/buttons/fields) and why the official API is not an option (partner agreement plus per-API certification). It does not cover auth requirements, rate limits, or what happens if the user's plan/screens differ from the returned steps.

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 step-by-step-return content and the API-partner caveat both earn their place, but the lead sentence is marketing-flavored and slightly misleading, and the API paragraph including 'checked 11 Oct 2026' is longer than the decision it supports. The key clarification (it doesn't act itself) arrives after the misleading opener rather than being front-loaded.

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 guidance tool with no output schema, the description covers the essentials: what is returned and which tools execute the change. What is missing is how the target SiteMinder account/property is identified given the empty schema, and any caveat about the returned steps being advisory rather than guaranteed to match the user's UI.

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 there is nothing for the description to disambiguate; the 0-param baseline of 4 is slightly tempered because the description also doesn't clarify how the target property/account is implicitly determined when no arguments are supplied.

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 (inventory) and clarifies the actual behavior: it returns step-by-step instructions (screens, buttons, fields) rather than performing the update. That distinguishes it from the cotlet_browser_* action tools it hands off to. The opening sentence ('Update inventory... from ChatGPT, Claude or any AI agent') reads as if the tool performs the mutation, which is only corrected in the next sentence, and it does not explicitly separate itself from siblings like siteminder_update_rates or siteminder_close_dates.

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 the workflow plainly: this tool gives the procedure, then the actual action happens via cotlet_browser_* in the user's SiteMinder Cloud Browser. The API note explains why the browser route is used instead of an official API, which is useful decision context. It does not explicitly say when to prefer a different inventory/rates sibling, so the routing guidance is contextual rather than exhaustive.

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