Search Zendesk Users

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, ensuring the agent knows it's a safe, idempotent read operation. The description adds behavioral context by mentioning 'Returns total count' and hinting at the Zendesk query syntax, which goes beyond annotations.

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 description is a single concise sentence that front-loads the key action and resource. No unnecessary words; every part adds value.

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 the tool's complexity (search with query syntax, pagination) and lack of output schema, the description is insufficient. It only mentions 'Returns total count' but omits details about the returned user list structure, pagination behavior, or query syntax examples. A more complete description would explain output fields and pagination.

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% with each parameter described. The description adds minimal value beyond the schema by providing examples (name, email) but does not clarify query syntax or pagination details. Baseline 3 is appropriate.

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 the tool's purpose: 'Search for users by name, email, or other criteria using Zendesk search query syntax.' It specifies the resource (users), the action (search), and the method (query syntax), effectively distinguishing it from sibling search tools like search_articles or search_tickets.

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 implies usage (searching users) but does not explicitly state when to use this tool versus alternatives like 'search' (which may be broader) or other specific search tools. No guidance on when not to use or prerequisites is provided.

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