user_list

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

Discloses that the tool returns profile info, which is necessary given the lack of output schema. However, omits critical behavioral details like pagination, result limits, or permissions required, bearing full burden since no annotations exist.

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?

Two well-structured sentences with no wasted words. Information is front-loaded with the action (Query) and resource (Operaton users) in the first sentence.

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?

While it mentions return values (helpful without output schema), it fails to address the parameter discrepancy or explain pagination behavior essential for a list operation. Incomplete given the schema/annotation poverty.

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?

Description mentions query capabilities by id, firstName, lastName, email, and group membership, but the input schema has zero parameters according to context signals. This creates a misleading mismatch between described functionality and actual schema.

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 the tool queries Operaton users and returns profile information. Distinguishes from sibling `user_getProfile` by implying a search/list operation ('each matching account') rather than a single lookup.

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 no guidance on when to use this versus `user_getProfile` or other user-related tools. No mention of prerequisites or filtering behavior despite implying query capabilities.

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