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

With no annotations and no output schema, the description carries the full burden of disclosing behavior, but it only states 'Search Users.' It does not mention pagination, the meaning of a trimmed response, potential rate limits, or what a user result looks like.

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 a single phrase, but it is under-specified rather than concise. It wastes the opportunity to provide useful context in the two words it uses, essentially repeating the tool name, so it fails to earn its place.

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?

The tool has a search functionality with pagination and a trim option, but the description does not explain return data, pagination behavior, or any special cases. Given the lack of an output schema and rich sibling context, this description is severely 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?

The input schema already provides descriptions for all three parameters (query, trim, cursor), so the schema coverage is 100%. The description adds no additional meaning beyond what the schema already states, so I give a baseline of 3.

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 'Search Users' is essentially a plain-English restatement of the tool name, providing no additional detail about what the search does, what platform or scope it covers, or what distinguishes it from sibling tools like scrapecreators_search_users_get or scrapecreators_search. It names a verb and resource but lacks any specificity.

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?

There is no information about when to use this tool versus alternatives, such as scrapecreators_search_users_get or scrapecreators_search. No context or exclusions are provided, leaving the agent without guidance.

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