list_project_users

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

Discloses that no admin permissions are required and that it works for any project viewer. Lacks details on whether the list is complete or paginated, and does not explicitly state read-only behavior.

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?

Three clear sentences with no redundancy. Front-loaded with the main action and result, followed by project specification and use cases.

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?

Explains output format (user_id+username pairs) and how to use it. Lacks mention of any filtering or error cases, but adequate for a simple list tool with no output schema.

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 100%, so baseline is 3. Description adds value by explaining the fallback to .kanboard.yaml and that both parameters are optional, which is not in the schema descriptions.

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?

Clearly states it lists Kanboard project members as user_id+username pairs. Distinguishes from sibling tools like add_project_user and remove_project_user by focusing on listing. Also ties to use cases (assign tasks, comments).

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?

Provides clear context on when to use (need user IDs for assignment/comments) and how to specify the project. Does not explicitly mention when not to use or alternatives, but the purpose is well-defined.

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