keap_list_users

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does reveal the operation is a GET request (read-only) and includes pagination parameters, but it omits details about authentication, rate limits, or default behaviors of filters like include_inactive or include_partners.

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 concise and well-structured, leading with the core purpose and then providing the API endpoint and parameter definitions. Every line is relevant, and there is no wasteful or redundant text.

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 operation with optional pagination and filter parameters, the description provides sufficient detail to understand what the tool does and how to invoke it. The existence of an output schema covers return values, so the lack of explicit return documentation is acceptable.

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 no descriptions (0% coverage), so the description's Args section attempts to explain each parameter. It adds minimal meaning (e.g., 'Max results per page' for limit) but largely restates the parameter names, offering only basic clarification.

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 'List users of the Keap app', providing a specific verb and resource. It distinguishes itself from sibling tools that list other entities (contacts, tags, etc.) by focusing on users, though it does not explicitly contrast with any particular sibling.

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. It does not mention any exclusions, prerequisites, or comparisons with sibling list tools, leaving the agent to infer usage solely from the tool name.

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