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

Annotations already declare readOnlyHint/idempotentHint/non-destructive/non-open-world, and the description reinforces this by saying it 'opens nothing by itself' and produces instructions rather than data. It adds genuinely useful context beyond annotations: the dependency on the Cloud Browser tool family and the constraint that Phorest API credentials only come via Phorest Support and require an in-house dev team. Minor gap: it does not say how long or how structured the returned steps are.

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 facts are front-loaded, but the opening clause 'from ChatGPT, Claude or any AI agent' is filler, and the long semicolon-chained sentences plus the 'checked 8 Nov 2026' parenthetical (a future date) make it harder to parse than necessary. The key behavioral fact — that this only returns instructions — is buried mid-sentence rather than stated first.

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 zero parameters, no output schema, and full annotation coverage, the description covers what an agent needs: what is returned, that nothing is opened, and which tools execute the actual work. It could be stronger by stating whether the steps are Phorest-version-specific or what to do if the screens don't match.

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 meaning to add and the baseline applies. The description correctly implies no inputs are needed to obtain the steps.

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 makes clear that this is a guidance tool, not a data-fetch: it 'returns how to do it in Phorest step by step (screens, buttons, fields) and opens nothing by itself', which resolves the ambiguity in the name 'List clients'. It names the resource (clients in the user's Phorest account) and the follow-up tool family (cotlet_browser_*), though it does not explicitly distinguish itself from cotlet_app_guide, which reads as a similar instructional sibling.

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 states the usage chain clearly: call this first to get steps, then perform the action with cotlet_browser_* tools in the user's Phorest Cloud Browser. What is missing is an explicit exclusion — when an agent should prefer cotlet_app_guide or the other phorest_* tools, and whether this is ever needed if the agent already knows the flow.

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