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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds meaningful behavior beyond that: it explicitly states the tool 'opens nothing by itself' and that its output is step-by-step UI instructions, which tells the agent it must chain into cotlet_browser_* calls. It does not describe the shape or length of the returned guidance, keeping it short of a 5.

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 operational content is front-loaded and compact, but the trailing sentence about Gorgias's REST API and an 'MCP server in open beta since May 2026' is marketing/context noise that does not help invoke this tool and even suggests an alternative path the agent cannot take. The 'from ChatGPT, Claude or any AI agent' framing is also filler.

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 rich annotations, the definition needs mainly to explain the nature of the return value and the follow-up workflow, which it does. What it omits is how the guidance maps to a specific ticket or query (the tool accepts no search terms, yet is named 'search'), leaving an unresolved gap about how the agent specifies what to search for.

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; per the baseline for a 0-parameter schema this sits at 4. The description correctly implies no inputs are needed.

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 opening clause 'Search tickets in the user's own Gorgias account' restates the name and implies the tool performs a search, but the real behavior is disclosed only mid-sentence: it 'Returns how to do it in Gorgias step by step (screens, buttons, fields) and opens nothing by itself.' The actual function (returning procedural guidance rather than ticket data) is real and specific, but it is buried and in tension with the name, so an agent skimming could misfire.

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?

There is a clear next-step directive ('then do it with the cotlet_browser_* tools in the user's Gorgias Cloud Browser'), which is useful. However, there is no guidance on when to use this versus the sibling action tools (gorgias_update_ticket, gorgias_reply_to_ticket, gorgias_apply_macro) that presumably also operate on tickets, and no statement of prerequisites or exclusions.

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