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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention what the tool returns, how pagination works, whether it mutates data, requires authentication, or any other behavioral trait. The phrase 'Search by Keyword' provides no information beyond the input parameter name.

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 but constitutes under-specification rather than effective conciseness. It does not earn its place because it adds no information beyond the tool name. It is a single missing-content phrase, not a well-structured, informative summary.

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 6 parameters, no output schema, and no annotations, so the description is the only source of context. It entirely fails to explain the search domain, expected response shape, or the meaning of optional parameters. The agent cannot safely or correctly invoke this tool without additional documentation.

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 coverage is 100%, so the baseline is 3 even with no parameter info in the description. However, the description adds no semantic value beyond the schema; it simply repeats the notion of a keyword, which is already documented in the 'query' parameter. The optional parameters (trim, cursor, region, sort_by, date_posted) remain unexplained in the context of this specific search.

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 by Keyword' is a tautology that merely restates the tool name without indicating what is being searched (e.g., creators, posts, ads). It completely fails to distinguish this tool from the many sibling search tools such as scrapecreators_search, scrapecreators_search_by_hashtag, and scrapecreators_search_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?

No guidance is provided on when to use this tool versus alternatives. The description offers zero context about the target entity, use cases, or exclusions, making it impossible for an agent to choose this tool among the long list of similar search-related siblings.

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