list_users

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

Annotations already provide readOnlyHint=true, so the description doesn't need to restate that. However, it adds value by specifying that listing requires an owner API key, which is a behavioral constraint not covered by annotations. This informs the agent about access privileges.

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, front-loaded sentence with no wasted words. It states the verb, resource, key detail (global roles), and the critical auth requirement efficiently.

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 tool with 3 parameters and no output schema, the description covers the essential purpose and auth requirement. However, it could be more complete by mentioning default behavior (e.g., includeRole defaults true) or suggesting related tools for context. The schema fills in the gaps, so overall adequate.

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% with clear descriptions for all three parameters (includeRole, projectId, maxItems). The description adds only marginal value by referencing 'global roles' which maps to includeRole, but otherwise does not enhance understanding beyond the 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 explicitly states the verb 'list' and the resource 'users', and adds specific context about global roles and the requirement for an owner API key. It clearly distinguishes from sibling tools like get_user (single user) or create_user (different operation).

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 mentions the auth requirement (owner API key) but does not provide explicit guidance on when to use this tool versus alternatives (e.g., get_user for a specific user, or other list tools). The usage context is implied but not elaborated.

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