Find users

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

With no annotations, the description carries the full burden. It does add useful behavioral context: environment-specific search fields and that the output is account IDs/usernames usable for assignment. However, it omits details like whether this is read-only, case sensitivity, pagination behavior, or error handling.

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?

A single, front-loaded sentence with no fluff. Every clause adds information: what is searched, the environment difference, and the output purpose.

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?

For a simple two-parameter search tool, the description covers the core purpose and return value. It is less complete because it does not mention result limits or how to choose between this and get_user, and there is no output schema to clarify the response shape.

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 coverage is only 50% (query is documented; maxResults is not). The description adds important semantics for query by distinguishing Cloud vs Data Center behavior, which is beyond the schema. It does not add any meaning for maxResults, though the schema's default/min/max partially compensate.

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?

Description clearly states a search verb and the user resource with specific searchable fields (name/email/username), and notes Cloud vs Data Center differences. It is distinct from sibling get_user because it is a search, not a single-user fetch, though it does not explicitly name that sibling.

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 phrase 'usable for assignment' implies the intended use case, but the description does not explicitly say when to prefer find_users over get_user or when not to use it. There is no exclusion or alternative routing guidance.

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