edubase_post_user

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

The description only restates the action (Create) which is consistent with annotations (readOnlyHint=false). However, it fails to disclose important behaviors beyond annotations, such as notification behavior (notify parameter), password generation, or immediate activation of the account. The description adds no value beyond what annotations already indicate.

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 concise (one sentence) but lacks structure. It achieves efficiency but at the cost of omitting necessary details like usage guidelines and behavioral context.

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 complexity (18 parameters, many options), the description is incomplete. It does not explain the return value (though output schema exists), prerequisites like required permissions, or interactions between parameters (e.g., when notify triggers email).

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 100%, so the schema already documents all parameters. The description adds no additional meaning or context beyond the schema, meeting the baseline expectation.

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 the action (Create) and the resource (new EduBase user account). It is specific and distinguishes from siblings like edubase_patch_user (update) and edubase_get_user (retrieve).

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 provides no guidance on when to use this tool versus alternatives, such as when to use edubase_post_user_assume or how to handle existing users. No context for exclusions or prerequisites is given.

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