get_users

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

With no annotations provided, the description carries the full behavioral disclosure burden, but it only states that the tool retrieves a list of users. It does not mention pagination, default filtering behavior, response format, volume limits, or whether an empty list vs. an error occurs on no results.

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 efficient sentence with no wasted words, and the core purpose is front-loaded. It is appropriately sized for a simple read tool, though it contains no additional supporting details.

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?

The tool has three optional filter parameters and no output schema, yet the description provides only a one-line purpose statement. Given the absence of annotations, an agent lacks sufficient context about how filters interact, what data is returned, and what caveats apply.

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%, with all three parameters (status, created_to, created_from) already documented in the schema. The description itself adds no extra meaning about parameter usage, combination rules, or formatting nuances, so the baseline score of 3 applies.

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 clear purpose: 'Получение списка пользователей GetCourse' (Getting a list of GetCourse users), which is a specific verb+resource pairing. However, it does not distinguish itself from any sibling tools, and no sibling names were provided to allow for differentiation.

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 gives no guidance on when to use this tool, what scenarios it fits, or which alternatives might be better suited. An agent gets no context about conditions that would make this tool the right choice.

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