Zendesk Unified Search

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

Annotations already declare readOnly true, idempotent, and non-destructive. The description adds behavioral details beyond annotations: paginated results (100 per page), total count, and that organization results are partial. This provides useful context without contradiction.

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 concise sentences, no wasted words. Each sentence adds distinct value: purpose, filter examples, and limitation with alternative. Front-loaded with core functionality.

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?

Given no output schema, the description adequately covers return values: total count, paginated results, and partial org data. It could specify full vs partial for tickets and users, but it's reasonable to assume they are complete.

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 coverage is 100%, so baseline is 3. The description adds value by showing example filter syntax (type:ticket, role:agent) and stating pagination behavior, going beyond the schema descriptions.

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 clearly states it searches across tickets, users, and organizations, using a specific verb and resource. It distinguishes from sibling tools like search_tickets, search_users, and search_articles by being a unified search, and provides example filters.

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 explains when to use this tool (initial search) and when to use alternatives (get_organization for full details). It also clarifies pagination and filter syntax, giving explicit usage guidance.

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