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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the call performs no UI action ('opens nothing by itself'), returns an instructional payload with screens/buttons/fields, and cannot be replaced by SiteMinder's public API due to partner certification. What's missing is the shape/size of the returned guidance (single step list vs. multi-screen reference).

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 key constraint ('returns how to do it step by step, opens nothing by itself, then use cotlet_browser_*') is front-loaded and useful. But 'from ChatGPT, Claude or any AI agent' is filler, and the trailing SiteMinder API paragraph is long and largely tangential, including a verification date and partnership-certification detail that most callers will not need to act on.

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?

With no parameters, no output schema, and annotations covering safety, the description carries the burden of explaining what comes back, and it does: a step-by-step procedural answer plus a handoff to browser tools. Completeness is only slightly short of ideal because the granularity and limits of the returned guidance are not described.

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 input schema has zero properties, so there is nothing for the description to disambiguate; baseline for a 0-parameter tool applies. The description correctly implies no arguments are needed to obtain the guidance, which is consistent with the empty schema.

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 (channel performance in SiteMinder) and then immediately clarifies a non-obvious truth: the tool returns a step-by-step how-to ('screens, buttons, fields') rather than the performance data itself. That distinction separates it from the siteminder_* action tools and the cotlet_browser_* tools. It loses a point only because the title and first clause ('Get channel performance') still read like a data-fetching tool, so the real purpose has to be inferred from the second sentence.

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?

The description explicitly states the workflow position: this tool opens nothing by itself, and the actual work is then done with the cotlet_browser_* tools in the user's SiteMinder Cloud Browser. It also rules out the official API path for this task by explaining the partner/certification requirement. It does not, however, say when to prefer this over the sibling siteminder_list_reservations or siteminder_update_* tools, so routing among SiteMinder tools remains implicit.

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