Get user info

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only the implicit notion of the authenticated user ('current'), without stating auth requirements, what is returned, or failure behavior for unauthenticated calls.

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?

A single short sentence with no wasted words and the key qualifier ('current') up front. It is terse to the point of under-specification, but that is penalized in completeness rather than here.

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 agent has no idea which user fields are returned (id, display name, email, groups?), which is exactly what a 'get info' tool should hint at. Given the trivial parameter surface and full annotation coverage, this gap is the only meaningful one, but it is real.

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 zero parameters, so the baseline is 4 and there is nothing to document. The word 'current' usefully confirms that no user identifier is accepted and the caller's own identity is used, which is a small but genuine addition.

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 is essentially a restatement of the tool name and title ('Get user info'), though the word 'current' does add a real scope qualifier that distinguishes it from nextcloud_get_user_quota and nextcloud_get_properties. It does not say what 'info' includes or how it differs from the quota sibling, so an agent still has to infer the distinction.

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 guidance on when to call this versus nextcloud_get_user_quota or nextcloud_get_properties, both of which return user-adjacent data. No prerequisites or exclusions are stated; the agent must guess based on names alone.

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