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 valuable context beyond that: it performs no action itself, it returns a concrete recipe of screens/buttons/fields, and it must be paired with browser tools to take effect. The API credential caveat is useful for planning, though it reads as catalog trivia rather than behavior of this call.

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 most decision-relevant fact — that the call only returns instructions and opens nothing — appears early, right after the purpose statement. The final sentence about the official API is longer and denser than needed and could be trimmed. No filler or repetition otherwise.

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 input schema and no output schema, the description must explain the return value, and it does so concretely (step-by-step screens, buttons, fields). It also closes the loop on how the task actually gets done via cotlet_browser_* tools. An agent could call this correctly and know what to expect as a result.

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 the schema coverage is 100%, so there is no parameter meaning to add. The description correctly implies no inputs are needed and instead spends its words on what the call returns. Baseline of 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?

Names a specific verb and resource (configure offer discount codes) and immediately clarifies the real output: step-by-step instructions for screens, buttons and fields in Club OS. That clarification is essential because the name implies an action the tool does not perform. It does not distinguish itself from the many sibling club_os_configure_* tools, which is the main gap.

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 clear operational context: call this to learn the procedure, then execute it with cotlet_browser_* tools in the Cloud Browser. It also rules out the API path by explaining credentials require emailing Club OS support. It stops short of explicit when-not-to-use guidance or naming a sibling alternative for related configuration tasks.

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