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

No annotations exist, so the description carries the full behavioral burden. It implies a read-only reference lookup but never says so, and gives no information about the shape of the response, whether results are static or fetched live, or any auth/rate constraints.

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?

One tight sentence, front-loaded with the toolbox tag and then the substance. The bracket tag is mild overhead but the operator list and engine list carry real information with no wasted prose.

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 single-parameter lookup with no output schema, the description needs to cover what is returned and how the filter works. It covers the content reasonably but leaves the parameter behavior and usage context unspecified.

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% for the single engine parameter, so the description must compensate. It does list the four engine names (Google, Bing, Yahoo, Baidu), indirectly giving meaning to the enum values, but it never says the parameter is optional or what happens when it is omitted.

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 names a concrete resource and scope: a support/cross-reference table for search operators (site:, filetype:, intitle:, before:) across Google, Bing, Yahoo and Baidu, plus deprecated operators. An agent can tell this is a reference-lookup tool rather than an action tool like seo__build_search_urls. It is clear but lacks an explicit verb and does not contrast itself with the closest sibling.

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 statement of when to call this versus alternatives such as seo__build_search_urls or seo__serp_preview, nor any exclusion or prerequisite. Usage is only inferable from the name and content description.

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