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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is known; the description adds real value by clarifying that nothing is executed, that the response is step-by-step UI instructions, and that execution is delegated to the browser tools. The only shortfall is that it doesn't state what the returned instructions look like (format, length) or what the browser tools require.

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 operative content is front-loaded and clear: what it returns, that it opens nothing, and the follow-up tools. But the final API-research sentence ('404 on 11 Nov 2026… help center has no Gymdesk API article') is lengthy justification that doesn't help an agent select or invoke the tool, and dates that far in the future read as noise.

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 guidance tool, the description covers the essentials: no side effects, instruction-style return content, and the required browser-tool follow-up. Minor gaps remain around how the member is scoped without any identifier parameter and whether the caller needs an authenticated Cloud Browser session.

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 parameter semantics to explain and the baseline is 4. The description does not explain how the target member is identified (presumably from conversation context), but with an empty schema there is nothing to document.

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+resource (freeze a member in the user's Gymdesk account) and then corrects the natural reading by saying the tool 'Returns how to do it in Gymdesk step by step (screens, buttons, fields) and opens nothing by itself.' An agent can tell this is a guidance/instruction generator rather than a mutating action. It stops short of naming a sibling such as unfreeze or bulk freeze, so it is clear but not differentiated.

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?

Usage is implied rather than prescribed: the description says to follow up with 'the cotlet_browser_* tools in the user's Gymdesk Cloud Browser', which gives a concrete next step. However, it never states when to prefer this tool over gymdesk_unfreeze_a_member or gymdesk_bulk_freeze_cancel_or_reactivate_members, nor any preconditions (e.g., plan type, member status required for a freeze).

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