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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds genuinely new behavior context by stating it "opens nothing by itself" and returns the procedure (screens, buttons, fields), which prevents an agent from assuming the profile is actually fetched.

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 core clarification (returns instructions, opens nothing, follow up with browser tools) is front-loaded and effective. But "from ChatGPT, Claude or any AI agent" is filler, and the closing sentence about ClubReady's official API and real-time data notifications is vague and does not help an agent decide or act.

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 tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields) and what is not done (nothing is opened). An agent has enough to call it correctly and know the next step, with the only gap being how it relates to the sibling ClubReady lookup tools.

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 nothing for the description to disambiguate beyond what the empty schema already shows. Baseline of 4 applies.

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 states a specific verb and resource ("View a customer profile") and immediately clarifies the actual mechanism: it returns step-by-step instructions rather than performing the view. That clarification distinguishes it from the cotlet_browser_* action tools, though it does not distinguish it from sibling lookups like clubready_view_customer_amenities or clubready_search_customer_or_prospect_profiles.

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 a usable workflow cue: read the steps here, "then do it with the cotlet_browser_* tools in the user's ClubReady Cloud Browser." That is real when-to-use context. However, there is no guidance on when to choose this over the sibling search or amenities tools, and no exclusions.

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