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

Annotations are absent, so the description carries the full burden of behavioral disclosure. The description only states 'Search Users,' which implies a read-only operation but reveals nothing about result format, pagination, limits, authentication, or other important behaviors. This is insufficient for a tool with no structured metadata support.

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 extremely short at two words, making it concise without any wasted words. However, it is under-specified, functioning more like a label than a complete sentence. It is front-loaded with the verb and object but lacks the detail that would make it appropriately sized for a tool description.

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?

There is no output schema, and the description fails to explain what the search returns, any constraints, or how it differs from other search tools. Given the tool's low complexity, a brief note on expected results would be sufficient, but this is entirely missing. The description is inadequate for an agent to fully understand the tool's behavior.

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 schema fully documents the single 'query' parameter with the description 'Username to search for,' achieving 100% schema description coverage. The tool description adds no new semantic information about the parameter, so it remains at the baseline of 3. There is no need for additional parameter explanation beyond the schema.

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' clearly identifies the action (search) and resource (users). However, it does not distinguish this tool from the sibling 'scrapecreators_search_users' or other search tools, which is a lack of specificity. A more descriptive version would mention the platform or context, but the basic intent is clear.

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 is provided on when to use this tool versus alternatives like 'scrapecreators_search_users' or other search utilities. There is no mention of use cases, such as finding creators by username, nor any exclusions or alternatives. This leaves the agent without clear decision-making support.

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