List platform users

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

The annotations already declare readOnlyHint and idempotentHint, so the read-only behavior is covered. However, the description adds no additional behavioral context such as whether the query parameter supports filtering, pagination, or authentication requirements. It does not contradict annotations but provides zero extra disclosure.

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 concise sentence with no redundant words. It is front-loaded and immediately communicates the action and resource, making it easy to scan.

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 is relatively simple, but the opaque query parameter and lack of output schema leave important gaps. The description does not explain the meaning of the query object, what data is returned, or any usage nuances. The minimal description is insufficient for an agent to confidently invoke the tool with the correct parameters.

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 schema has a single 'query' object parameter with 0% description coverage, and the description does not mention or explain this parameter at all. There is no hint about what fields the query object accepts or how filtering works. The description completely fails to compensate for the schema's lack of parameter details.

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 uses the specific verb 'List' with the resource 'Cymulate platform users,' clearly stating the tool's action. However, it merely restates the title with the addition of 'Cymulate' and does not differentiate among the many sibling list tools. It lacks any scope qualifiers but is unambiguous about the core 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?

The description provides no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It simply restates the function without mentioning use cases such as retrieving all users or comparing to other info tools like cymulate_info_activity_center.

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