list_users

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

No annotations are provided, so the description must carry the full burden. It states 'List users', implying a read-only operation, but provides no details on sorting, pagination, rate limits, or authentication requirements. The top parameter (default 0) is not explained, leaving behavioral ambiguity.

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 very short with two sentences and no fluff, but it is too sparse. Conciseness is achieved at the expense of completeness; important information about parameters and usage is omitted.

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 presence of an output schema (not visible), the description could rely on it for return values, but it still fails to explain pagination (top default 0), sorting, or the full scope of OData filtering. For a read-only list tool with no annotations, the description is insufficient.

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?

With 0% schema description coverage, the description must compensate. It mentions filter_expr for OData filtering, which adds some meaning, but does not explain the top parameter (page size). The description only partially clarifies the parameters, missing significant semantic value.

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 the verb 'List' and resource 'users', which is specific and distinct from sibling tools like list_clients. However, it lacks any additional context about what constitutes a 'user' (e.g., system accounts vs. contacts), preventing a 5.

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 only guidance is 'Use filter_expr for OData filtering', which is minimal. There is no mention of when to use this tool versus alternatives like get_user for a single user, or exclusions like not for filtering by other criteria. The description fails to distinguish its use case from the many sibling list tools.

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