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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the underlying REST call (GET /search.json), which is minor context, but says nothing about result shape, pagination behavior (despite a page parameter), or rate limits. With annotations carrying the safety burden, this is adequate rather than rich.

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?

Two tightly packed sentences: scope first, then concrete syntax examples, then the endpoint reference. No filler, and the most important information (what it searches and how to phrase the query) is front-loaded.

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 output schema, the description should ideally say something about what a result looks like or how pagination behaves (a page parameter exists and is undocumented behaviorally). Safety is covered by annotations and query construction is well covered, but the return/paging side is left entirely implicit.

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?

Schema description coverage is 100%, so the baseline is 3 and the schema already documents query, page, sort_by and sort_order. The description adds value by demonstrating multi-type query syntax (`type:user email:...`, `type:organization name:...`) beyond the single ticket example in the schema, clarifying how the required query parameter is constructed for non-ticket entities.

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 (search) and resource scope (tickets, users, organizations, groups) with the mechanism named (Zendesk search syntax). It is clearly distinguishable from narrow siblings like zendesk_search_users (users only) or zendesk_list_tickets (no query syntax), so an agent can route without opening schemas.

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 'unified search' framing implies when this cross-entity tool is preferable to the single-entity list/search siblings, and the examples show realistic query contexts. However, there is no explicit when-to-use or when-not-to-use guidance versus zendesk_search_users or zendesk_list_tickets, leaving selection to inference.

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