redmine_list_users

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

States 'Read-only' and 'Requires admin privileges', but does not disclose pagination behavior, rate limits, or data format. With no annotations, this is minimal transparency.

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?

Concise single sentence plus parameter list. Could integrate 'Read-only' and 'admin only' more efficiently, but overall well-structured.

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?

Covers purpose, auth, and parameters well. Lacks usage guidelines and behavioral details, but output schema exists to explain returns. Adequate but missing context about siblings.

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 coverage is 0%; description compensates fully by explaining each parameter, including valid values for status and defaults. Highly informative.

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?

Clear verb+resource and scope 'List users (admin only)', but lacks differentiation from siblings beyond name. Parameter details reinforce purpose.

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?

No explicit guidance on when to use this vs alternatives like list_groups or list_projects. Only mentions 'admin only' for auth context.

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