Get user

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds only the raw HTTP endpoint (GET /ocs/v2.php/cloud/users/{user_id}), which gives a hint about the API surface but omits permission requirements, behavior for unknown user IDs, and what data is returned.

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?

Two short lines, front-loaded with the purpose and followed by the endpoint. No filler or redundancy; every line contributes information.

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?

With no output schema, the description should at least hint at what account fields come back, and it does not. Combined with the absence of permission and format details for the sole parameter, the definition is adequate but leaves real gaps for an agent to guess around.

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 single user_id parameter has 0% schema description coverage, so the description must carry the load. The path template shows that user_id identifies the account in the URL, but it does not clarify whether it is a username, numeric ID, or email format — a meaningful gap for the only required input.

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?

States a concrete verb and resource: "Read one account's details", which is clearly a single-user lookup versus a listing. However, it does not distinguish itself from close siblings like nextcloud_get_user_info or nextcloud_get_user_quota, so an agent cannot tell which single-user endpoint to pick without inspecting schemas.

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?

There is no explicit when-to-use guidance, no prerequisites (such as admin privileges typically required by the OCS cloud/users endpoint), and no mention of when to prefer nextcloud_get_user_info or nextcloud_list_users. Usage is only vaguely implied by the phrase "one account's details".

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