get_users

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool retrieves a user list, but does not mention any constraints, side effects, performance characteristics, or response format. For a read operation this is minimal, but it lacks transparency about anything beyond the basic action.

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, concise sentence with no redundant words. It is front-loaded with the action and resource, making it immediately scannable. Every word earns its place.

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 simple list retrieval tool with one parameter and no output schema, the description is minimally adequate. However, it omits details like the structure of the returned users, any permissions needed, or whether pagination is handled via the limit parameter. Given the absence of annotations, more context would improve completeness, but the simplicity of the tool makes this a borderline 3.

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 coverage is 100% (the limit parameter is described in the schema as 'Количество пользователей'). The description adds no extra meaning beyond what the schema already provides. Baseline of 3 is appropriate since the schema fully documents the parameter.

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 verb ('Получить' = get) and a specific resource ('список пользователей Mango Office' = list of Mango Office users). It is unambiguous and distinct from the sibling tools (get_calls, make_call, etc.), which operate on calls and SMS. The purpose is immediately obvious.

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, or any usage context such as pagination, authentication requirements, or typical scenarios. It simply states what it does, leaving the agent to infer when it is appropriate.

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