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

Annotations already establish readOnly, idempotent, non-destructive, closed-world. The description adds real context beyond them: it explains that nothing is opened or mutated, that the return value is procedural instructions, and that Zendesk offers no hosted MCP for ticketing. The only gap is that it never explains why a 'search' tool takes no query.

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 sentence ('Returns how to do it ... opens nothing by itself ... then do it with cotlet_browser_*') is well front-loaded and earns its place. The trailing sentence about Zendesk's REST API and the absence of a hosted MCP server is tangential background that dilutes focus, and the opening 'Search tickets' framing contradicts the body, forcing the reader to re-parse.

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 guide tool the essentials are covered: what it returns and which sibling tools execute the action. However, it omits the relationship to zendesk_list_tickets and leaves the user's prerequisites (signed-in browser session, account scope) unstated, which matters for a tool that defers execution to browser automation.

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 has zero parameters, so per the baseline there is nothing for the description to compensate for. The description implicitly accounts for that by framing the output as generic step-by-step guidance rather than a parameterized query. No meaningful gap.

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 the resource (Zendesk tickets) but the verb is muddled: the opening line claims to 'Search tickets', then the body clarifies the tool 'Returns how to do it in Zendesk step by step ... and opens nothing by itself'. So the real function – a how-to/guide tool, not a searcher – is disclosed, but only after a misleading lead. It also never distinguishes itself from the sibling zendesk_list_tickets, which an agent would reasonably assume performs the actual listing.

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 does name a follow-on path ('then do it with the cotlet_browser_* tools in the user's Zendesk Cloud Browser'), which is useful routing. But there is no guidance on when to choose this over zendesk_list_tickets, or on what a user must have set up before the browser steps apply. Usage is implied rather than stated.

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