kchat_get_users

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the call is a read returning 'basic profile information', which tells the agent what to expect, but says nothing about pagination limits, total counts, or whether results are filtered by visibility/permissions.

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?

A single front-loaded sentence with zero filler; the verb and resource come first and the return payload is appended compactly.

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, parameter-light read tool with no output schema, the description covers the operation and the shape of the result adequately. It falls slightly short on pagination expectations and scope caveats, which matter for a 'get all users' call with a hard 100-result cap.

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% (page and limit are documented with defaults and bounds), so the schema already does this work. The description adds no pagination or limit guidance, so the baseline 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?

States a specific verb ('Get') and resource ('list of all users') and adds what is returned ('basic profile information'). The word 'all' implicitly separates it from the single-user sibling kchat_get_user_profile, though that sibling is never named.

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?

Usage is only implied by 'all users' — an agent can infer this is the bulk-listing call versus kchat_get_user_profile, but the description never states when to choose one over the other or any preconditions (e.g. permissions, whether bot accounts are included).

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