zid_get_user

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

Annotations already declare readOnlyHint: true, and the description redundantly states 'Read-only.' No additional behavioral traits are disclosed (e.g., behavior on missing ID, response format). With annotations covering safety, the description adds minimal value beyond restating the hint.

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 sentence, front-loaded with the key action, and contains no unnecessary words. It is maximally concise while still being informative.

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 (1 required param, no output schema, annotations present), the description covers the essential purpose and read-only nature. It is adequate for an agent to understand basic usage, though it lacks details on error responses or return structure.

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 input schema has 0% description coverage for the user_id parameter. The description says 'by ID,' which indirectly informs that user_id is the identifier, but it does not add details like format or constraints. Compared to the schema, it provides marginal extra meaning.

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 explicitly states 'Get one ZIdentity user by ID,' which is a specific verb and resource. It clearly distinguishes from sibling tools like zid_list_users (list all) and zid_search_users (search by criteria) by focusing on retrieval by a single ID.

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 when a specific user ID is available, but it does not explicitly mention when to use or avoid this tool, nor does it reference alternatives. The context from sibling names provides some guidance, but the description itself offers no explicit usage boundaries.

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