find_users

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

Description does not disclose read-only nature, pagination (page_key), exact match behavior, or inclusion of disabled users. With no annotations, the agent has minimal information about side effects or safety.

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?

Single sentence, no wasted words. Verb and resource are front-loaded. Appropriate length for the tool's 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?

With 7 parameters, no output schema, and no annotations, the description is too brief. Missing critical context about pagination, result format, and filter behavior (exact_match, include_disabled).

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 adds meaning for 4 of 7 parameters (username, email, phone, employee_number) but ignores exact_match, include_disabled, and page_key. Schema coverage is 0%, so description partially compensates but is incomplete.

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 tool searches users, lists specific searchable fields (username, email, phone, employee number), differentiating from sibling tools like 'list_users' which likely lists all users, and 'get_user' which gets a single user by ID.

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?

No guidance on when to use this tool vs alternatives like 'list_users' or 'get_user'. No mention of prerequisites or when search is appropriate versus other user retrieval methods.

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