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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description does add genuinely useful behavior beyond them: the return is a step-by-step walkthrough of screens, buttons and fields, and nothing is opened or changed. The closing sentence about Gladly's REST API and the absence of an official MCP server adds no behavioral value for an agent invoking the tool.

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 first sentence front-loads the key fact that this is a guide, not an executor, which is exactly right. But it is a run-on sentence packing three ideas together, and the trailing note about Gladly's API version and MCP-server status does not earn its place in a tool description.

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 and annotations covering safety, the description supplies what matters: it describes the shape of the return (step-by-step screens, buttons, fields) and points to the browser tools for execution. It is close to complete, with only the vestigial API note detracting.

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 input schema has zero parameters, so the baseline of 4 applies. Nothing in the description contradicts or needs to supplement an empty schema.

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?

States a specific verb and resource (assign a conversation in Gladly) and then immediately clarifies the real behavior: it returns step-by-step instructions rather than performing the assignment. That resolves the tension with the name. It does not, however, distinguish itself from the other gladly_* siblings (close, add_note, apply_topics) beyond naming the cotlet_browser_* tools that execute the action.

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?

Gives clear usage context: call this to learn how to assign a conversation, then carry it out with cotlet_browser_* in the user's Gladly Cloud Browser. It implicitly excludes execution ('opens nothing by itself') but never states when this tool should not be used or which gladly_* sibling to pick for a different action.

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