workboard_list_users_tool

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

With no annotations, the description must disclose behavior. It states it lists all users and requires admin role, but lacks details on pagination, response size, or whether the list includes inactive users. This is adequate for a simple list operation but could be more comprehensive.

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 extremely concise: two sentences with no redundant information. Every sentence adds value: first states action and requirement, second states return type.

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?

The tool has an output schema but its content is not visible; the description only says 'List of all users' which is vague. For a list tool, it would benefit from specifying key fields returned (e.g., name, email, role). However, given the tool's simplicity and the presence of an output schema, the description is minimally sufficient.

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 zero parameters, so no parameter documentation is needed. The description adds no parameter info, but none is required. Schema coverage is effectively 100%.

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 'List all WorkBoard users' which specifies the verb (list) and resource (users). It distinguishes from sibling tool workboard_get_user_tool which retrieves a single user, and from create/update tools.

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 includes a role requirement ('requires Data-Admin role'), giving a clear prerequisite. However, it does not specify when to use this tool versus alternatives like workboard_get_user_tool for a specific user, or mention limitations like rate limits or data freshness.

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