zid_get_user

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

The 'Read-only' note is redundant with the readOnlyHint annotation, but the description adds the 'one' scoping, indicating a single result. No additional behavioral details (e.g., error handling, pagination) are provided beyond annotations, so minimal added value.

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 extremely concise, front-loaded, and every word adds value. 'Get one ZIdentity user by ID' and 'Read-only' together convey all essential information without waste.

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 simplicity of the tool (1 param, no output schema), the description is adequate but minimal. It doesn't mention return format or error behavior, but the action is straightforward and likely returns a user object. More detail could improve completeness.

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?

With a single parameter and 0% schema coverage, the description compensates minimally by indicating the parameter is the user's ID. It doesn't specify format or constraints, but it does clarify the purpose of 'user_id' beyond just a string type.

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 retrieves one ZIdentity user by ID, using a specific verb and resource. It distinguishes itself from list/search tools by emphasizing 'by ID' and 'one', aligning with its name and sibling tools.

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?

It provides clear context that the tool is for fetching a specific user by ID, implying knowledge of the user_id is required. However, it does not explicitly mention when not to use it or alternative tools like search, which would strengthen guidance.

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