apex_list_users

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds minimal behavioral context beyond the annotations, such as the fact that it lists 'all users' (unfiltered). However, it does not disclose potential behavior like pagination, ordering, or permission requirements, so it meets the baseline but does not exceed it.

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, direct sentence with no filler or redundancy. It immediately states the action and object, effectively front-loading the core purpose.

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 simplicity of the tool (one optional parameter, output schema present, rich annotations), the description is largely sufficient. It clearly indicates the tool's scope and action. However, it does not mention any prerequisites like being connected to an APEX workspace or authentication, which might be inferred from the presence of a separate apex_connect tool. This is a minor gap, so not a perfect score.

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 100% coverage, with workspace_id described as 'Workspace ID (defaults to configured workspace).' The tool description does not add any additional meaning to the parameter; it only repeats the workspace scope. With high schema coverage, the description does not need to compensate, so baseline 3 is appropriate.

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: 'List all users in the APEX workspace.' It uses a specific verb (List) and resource (users) along with a clear scope (APEX workspace), which distinguishes it from sibling tools like apex_create_user or apex_list_apps.

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 prerequisites, exclusions, or context such as 'use this when you need to review existing users before assigning permissions.' The usage context is entirely implied by the tool's name and purpose.

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