moodle_get_users

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

No annotations are present, so the description must fully disclose behavioral traits. It does not mention any aspects like pagination, rate limits, or whether it returns all users when no criteria are provided. Only the basic retrieval action is stated.

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 a single short sentence, which is concise but lacks necessary detail. It does not front-load critical information like parameter usage or output expectations, making it under-specified.

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 no output schema and incomplete parameter documentation, the description leaves significant gaps. It does not clarify what the tool returns, how filtering works, or any constraints, making it insufficient for reliable agent invocation.

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 input schema has 100% missing description coverage (0% described), and the tool description does not explain the 'criteria' parameter at all. There is no mention that it expects an array of objects with 'key' and 'value', nor what each key (id, username, email) represents.

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 states a specific verb ('Récupère' - retrieves) and resource ('liste d'utilisateurs Moodle' - list of Moodle users), making the purpose clear. However, it does not differentiate from sibling tools like moodle_get_enrolled_users, which also retrieves users.

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 use this tool versus alternatives such as moodle_get_enrolled_users or moodle_get_courses. No context or prerequisites are provided.

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