search_users

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

No annotations are provided, so the description must disclose behavioral traits itself. The description only states 'System-level operation for administrative purposes' which hints at scope but doesn't disclose whether the operation is read-only, destructive, rate-limited, or returns paginated results. For a search tool with 5 parameters and no annotations, this is insufficient.

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 concise at two sentences, front-loading the main purpose. However, the second sentence is somewhat generic and could be more informative. It earns its place but doesn't add much value.

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 5 parameters, no output schema, and no annotations, the description provides minimal context. It doesn't explain the search algorithm, sort order, whether results are paginated, or what fields are returned. For a search tool of moderate complexity, this is incomplete.

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 each parameter already has a description in the input schema. The tool description adds no additional context beyond what's in the schema parameters. With full coverage, baseline 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 clearly states 'Search for users with optional filters' which pairs the verb 'search' with the resource 'users'. The 'System-level operation for administrative purposes' provides additional scope that helps distinguish it from user-facing search. However, it doesn't explicitly differentiate from sibling tools like get_user or get_user_wallets.

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 provides no guidance on when to use this tool versus alternatives like get_user (which retrieves a single user) or other search tools. There is no mention of prerequisites, permission levels, or situations where this tool would be preferred. The 'for administrative purposes' hint is vague and doesn't replace explicit usage guidance.

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