get_users

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

No annotations are provided, so the description must cover behavioral traits. It mentions pagination and return format (JSON string for team activity analysis) but omits critical details like permission requirements, rate limits, or performance implications. The lack of annotation support leaves agents uninformed about safety and mutability.

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 at three sentences, with the main purpose front-loaded. It follows a clear structure (purpose, args, returns). Minor improvements could remove the redundant parameter listing since the schema already defines them.

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 the tool has 2 parameters with no enums, an output schema exists, and the tool is a list operation, the description adequately covers pagination and return format. However, it lacks details about sorting, filtering, or implicit ordering, which would help agents understand the full behavior.

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 description restates the parameter names and defaults that are already in the input schema. For simple integer parameters, this adds minimal value. With schema coverage at 0%, the description does clarify usage (e.g., 'maximum number' and 'skip for pagination') but does not go beyond the schema's own information.

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 'Get all users in the organization,' which is a specific verb and resource. However, it does not differentiate from sibling tools like get_user_info or get_user_count, which could lead to confusion about which tool to use for listing vs. single user retrieval.

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 like get_user_info or get_current_user. It only explains pagination parameters but lacks context for tool selection.

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