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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only states the tool is 'token-efficient', hinting at concise output, but does not disclose pagination behavior (cursor parameter), rate limits, authentication needs, or any side effects. The behavioral traits are insufficiently described.

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 very short (6 words) and to the point, but it sacrifices essential information. While it is concise, it is under-specified and lacks structure. The phrase 'Token-efficient search results (google/bing/yandex)' is a single sentence without front-loading of key details, and the brevity does not serve the agent well.

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 the tool has 5 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the tool returns, how to use the parameters, or any important behavioral constraints. The agent would have to guess or rely on the parameter names alone, which is insufficient for 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?

The schema has 0% parameter description coverage, meaning the parameter names and defaults are the only clues. The description provides no additional meaning for any of the five parameters (q, limit, cursor, engine, country). It does not explain what 'q' is, how 'limit' works, or the purpose of 'cursor' for pagination. The description adds zero value 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 clearly states the tool returns search results and mentions three major search engines (google/bing/yandex), indicating it performs web searches. However, it does not differentiate from sibling tools like 'local' or 'history' which may also involve search functionality. The verb 'search' is implied but not explicitly stated as a verb; the phrasing 'search results' is acceptable.

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 only mentions 'Token-efficient' as a potential usage hint, suggesting it favors compact results, but provides no explicit guidance on when to use this tool versus alternatives like 'context', 'local', or 'history'. No exclusions, prerequisites, or alternatives are mentioned.

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