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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, and the description reinforces this with "opens nothing by itself" — no contradiction, and the clarification is valuable given the mutating-sounding name. It adds useful ecosystem context (paid API & Webhooks module required, no official MCP server as of a dated check). It does not describe how detailed or structured the returned steps are beyond "screens, buttons, fields."

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?

Three sentences, front-loaded with the core behavior and the read-only caveat before the execution path. The final sentence on FreeScout's API status is somewhat tangential but earns its place by justifying why browser tools are required. No filler or repetition.

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 parameters, no output schema, and annotations covering safety, the description supplies what an agent needs: what it returns, that it changes nothing, and which tools to use next. The main remaining gap is that it never says which statuses are valid or that the returned guidance is generic across all statuses.

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; baseline is 4. The description does not address the notable implication of an empty schema — that the guidance is generic and not scoped to a specific conversation or target status.

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 resource (FreeScout conversation status) and clarifies the actual behavior: it returns step-by-step instructions rather than performing the change, and explicitly says it "opens nothing by itself." The verb "Change status" in the name/title is slightly misleading for a read-only guidance tool, but the description corrects it in the first two sentences. It differentiates itself from the cotlet_browser_* siblings by naming them as the follow-up execution path, though it does not distinguish itself from the freescout_* siblings.

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?

The description gives a clear two-step workflow: call this first to get the screens/buttons/fields, then perform the action with the cotlet_browser_* tools in the FreeScout Cloud Browser. It also explains why browser automation is the path (no official MCP server, API only via a paid module). It stops short of stating when NOT to use this tool or how it relates to the other freescout_* guidance tools.

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