Create user

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so the mutation profile is known. The description adds real value by explaining that supplying an email triggers a set-password invite rather than immediate activation, but it omits what happens when user_id already exists, what permissions are required, and what the call returns.

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 core behavior is front-loaded in one sentence with the main decision rule immediately after. The trailing raw endpoint line adds little for an agent but costs only a few tokens.

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?

For a multi-parameter account-mutating tool with no output schema and no parameter documentation in the schema, the description is too thin. It should at least identify user_id as required and characterize quota and groups, since an agent cannot infer their format or effect from anywhere else.

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?

Schema description coverage is 0% across six parameters, so the description carries the full burden, yet it only touches on password and email. It never explains user_id (the sole required parameter), quota, groups, or display_name, leaving half the surface undocumented in both places.

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 specific verb and resource ('Create one account') and is clearly distinguishable from the many sibling create_* tools by the account/user domain. It does not explicitly name neighbors like nextcloud_create_group or nextcloud_update_user, but the resource is unambiguous.

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?

Gives the key branch condition for the two provisioning paths (password vs. email invite), which implicitly tells the agent which parameter combination to use. It offers no when-to-use vs. alternatives framing and no note about following up with nextcloud_add_user_to_group when the groups parameter isn't used.

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