list_users

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

The description states the return format is Markdown, which adds value beyond the schema. However, without annotations, it does not disclose behavioral traits like permission requirements, whether it lists all users or only accessible ones, or any side effects. It is adequate but not thorough.

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 concise and structured with 'Args' and 'Returns' sections, making it easy to scan. It contains no superfluous content, though it could be slightly longer to include usage guidance.

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 the simplicity of the tool (one optional parameter) and the presence of an output schema, the description covers the essential behavior and return format. It is complete enough for an agent to use the tool effectively, though pagination beyond the limit parameter is not discussed.

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 description explains the 'limit' parameter as 'Maximum number of users to return' and mentions the default value of 100, which adds meaning beyond the schema (which has no description). The single parameter is well covered.

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 users on the Tableau Server,' which is a specific verb and resource. However, it does not distinguish itself from sibling tools like 'get_user' (which retrieves a single user) or other list tools, missing an opportunity to clarify scope.

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?

There is no guidance on when to use this tool versus alternatives such as 'get_user' for a specific user or other list tools. The description lacks context about scenarios where this tool is appropriate or not.

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