tocaro_search_users

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

With no annotations, the description carries the transparency burden. It discloses the search scope (same contract as bot creator), query behavior (prefix match), pagination limits, and return code format ('us' + 8 characters). It does not mention null-query behavior or ordering, but it is not misleading and covers the essential behavior.

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 four compact, purposeful sentences. It front-loads the main purpose and then adds parameter constraints and return-value usage without redundancy or filler.

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 optional-parameter search tool with an output schema present, this is nearly complete: it covers scope, query format, pagination bounds, and how results should be consumed. Minor gaps such as null-query semantics and result ordering are unlikely to prevent correct invocation.

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 for the missing parameter documentation. It adds meaning for query (email/username prefix search), page, and per_page (valid ranges). It does not explicitly state behavior when query is null, but the schema's default null and the described prefix-match semantics make the intent reasonably clear.

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 opens with a specific action and resource: searching for users in the same contract as the bot creator. This clearly distinguishes it from sibling tools such as tocaro_search_tasks and tocaro_get_group_members.

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?

It gives clear practical context: query performs prefix matching on email or username, and the returned user code is meant to be passed to tools like tocaro_post_message. It does not explicitly state exclusion conditions or alternatives, but it provides enough guidance for an agent to select it appropriately.

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