search_users

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

With no annotations provided, the description partially addresses behavior by stating it 'Returns user data matching the search criteria including linked accounts, MFA methods, and metadata.' It does not mention pagination, auth requirements, or output format, leaving gaps.

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 concise sentences, front-loaded with the purpose. Every phrase adds value with no wasted words.

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 4 parameters (none required), an output schema, and no enums, the description covers return content but omits search behavior (e.g., partial vs exact match) and whether multiple identifiers can be combined. Adequate but not exhaustive.

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 0%, so the description must compensate. It explains the mutual exclusivity of 'search_term' vs specific identifiers and lists the identifier types (emails, phone numbers, wallet addresses), adding meaning beyond the bare schema. Could add format constraints.

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 'Search for users by search term OR specific identifiers,' specifying the verb 'Search' and the resource 'users'. It distinguishes from siblings like 'get_user' (by ID) and 'list_users' (all 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?

The description explicitly instructs 'Use either search_term OR specific identifiers, not both,' providing conditional usage guidance. However, it does not contrast with when to use sibling tools like 'get_user' for exact matches.

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