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

Beyond the readOnly and non-destructive annotations, the description discloses that the tool returns screens, buttons, and fields, and that it performs no action itself. It does not describe the exact output shape, but given the annotations and zero-parameter schema, this adds meaningful behavioral context.

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 description is a compact paragraph that mostly front-loads the purpose and the browser-tool handoff. Some phrases, such as 'from ChatGPT, Claude or any AI agent' and the API-plan aside, add mild noise, and the key clarification that it opens nothing by itself arrives mid-sentence rather than immediately.

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 guidance tool with rich annotations and no output schema, it covers what to expect and how to proceed with the browser tools. The main remaining gap is that it does not state upfront that no client data is returned, which could briefly mislead an agent expecting an actual client list.

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?

There are no input parameters and schema coverage is 100%, so there is no parameter meaning for the description to add. The baseline for a zero-parameter tool is 4.

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 this tool returns step-by-step instructions for listing clients and explicitly says it 'opens nothing by itself,' which distinguishes it from the cotlet_browser_* action tools. However, the leading phrase 'List clients in the user's own Salonist account' initially suggests an actual data-listing operation, creating some ambiguity that is only resolved later in the 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?

It clearly tells the agent to use this tool first and then perform the action with the cotlet_browser_* tools in the Salonist Cloud Browser. It also adds API-plan context that helps explain why the browser route is needed, though it does not give explicit when-not-to-use conditions.

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