find_users

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

With no annotations provided, the description carries the full burden of disclosing behavior, but 'Find users' discloses nothing: no mention of search semantics, pagination, result format, or idempotency. It neither confirms nor denies any behavioral traits, but it fails to provide the transparency the agent needs.

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 short and front-loaded, but it is under-specified rather than efficiently concise. It consists of a tautological two-word phrase and provides no structured or scoped information that would help an agent invoke the tool correctly.

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 six parameters, zero required fields, no annotations, and no output schema, the description is far too incomplete. The agent is left unable to determine key invocation details such as which parameters are mutually exclusive, how paging works, or what the return value will be.

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?

Schema description coverage is 100%, so the schema alreadily documents the parameters, including the conditional requirement on accountId. The description adds no additional meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 'Find users' simply restates the tool name and provides no additional specification about which users are found, how matching works, or what scope the search covers. It does not differentiate this tool from related siblings like get_user or find_bulk_assignable_users.

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 about when to use this tool versus alternatives such as get_user or find_bulk_assignable_users. The description offers no context, prerequisites, or exclusions, leaving the agent to infer usage from the parameter schema alone.

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