list-users

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

With no annotations provided, the description carries the full burden. It discloses that it lists all users in the world (no filtering), and explains the special behavior of the 'landing scene' field (only shown when set; otherwise users follow the active scene). This provides important behavioral context beyond the simple list operation.

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, long sentence that front-loads the core purpose and enumerates fields. It is somewhat verbose but each detail serves a purpose (clarifying output and usage). It earns its length by providing significant information.

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 that there are no parameters and no output schema, the description fully covers what the tool does, what it returns, and when to use it. It mentions the field list and the landing scene exception, leaving no critical gaps for the agent to call it correctly.

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 tool has zero parameters, so there is no schema to compensate for, and the description already explains what data is returned. The description adds meaning to the output by enumerating all fields and clarifying the landing scene nuance, which is valuable given the lack of an output schema.

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 verb ('list') and resource ('user accounts'), enumerates the returned fields in detail, and distinguishes it from related tools like update-user and set-landing-scene. It goes beyond a generic 'list users' by specifying the exact data returned, making it easy for an agent to know what to expect.

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 explicitly states this tool is 'the read to run before update-user and set-landing-scene', giving clear guidance on when to use it. It does not mention when not to use it or list alternatives, but this context is strong enough to guide an agent.

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