Get Zendesk User

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

Annotations already provide extensive behavioral hints (readOnlyHint=true, destructiveHint=false, idempotentHint=true). The description adds no further behavioral traits; it simply affirms the retrieval operation. No contradictions with 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 with no unnecessary words. It is perfectly sized for the tool's simplicity.

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 simplicity (one parameter, no output schema, rich annotations), the description is complete enough to enable correct selection and invocation. No critical information is missing.

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 schema has 100% coverage with parameter description 'User ID', which is minimal. The tool description adds the phrase 'by ID' but does not enrich semantics beyond the schema baseline.

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 action (retrieve), the resource (user), and the method (by ID). This distinguishes it from sibling tools like get_current_user (which retrieves the current user without an ID) and search_users (which searches with other criteria).

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 implicitly indicates usage when you have a user ID, but it does not explicitly mention alternatives or when not to use this tool. The context from siblings (e.g., get_current_user, search_users) helps, but the description itself lacks exclusion guidance.

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