list_users

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

No annotations are provided, so the description carries the burden. It discloses the core function (listing employees) and the intended use case, but does not mention any limitations, auth requirements, or response details beyond the schema. For a simple read-only list tool, this is adequate but not rich.

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 two sentences long, with the purpose stated first and a clear usage directive second. There is no filler or redundancy; 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?

Given no output schema and no annotations, the description combined with the rich schema (detailed parameter descriptions) provides enough context for an agent to invoke the tool correctly. It explains when to use it and what it returns, but could be improved by mentioning response format or pagination limits, though the schema covers defaults.

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 baseline is 3. The description adds the context that the list is used for finding IDs by name, which aligns with the default fields (id, name, etc.), but it does not explain parameter syntax or behavior beyond what the schema already defines.

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 tool's function: 'Получить список сотрудников Planfix' (Get a list of Planfix employees). It also distinguishes the tool from siblings by specifying a concrete use case: finding an assignee's ID by name before create_task/update_task, which differentiates it from get_user (single user) or get_contacts.

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 explicit guidance on when to use the tool: 'Используй для поиска ID исполнителя по имени перед create_task/update_task' (Use for finding the assignee's ID by name before create_task/update_task). It does not mention when not to use it or alternatives like get_user, so it falls short of a 5.

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