sogou_search

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

Annotations already declare readOnlyHint=true and openWorldHint=true, providing a safe read-only profile. The description adds a key behavioral trait: it uses the user's real Chrome session, which implies dependence on session state, cookies, or login. This goes beyond annotation information without contradicting it.

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, front-loaded sentence that conveys the essential purpose and context. Every word earns its place, with no filler or repetition of schema fields, making it highly concise and well-structured.

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's simplicity, the description provides enough context for an agent to select it appropriately, especially with annotations and an output schema present. The main gap is parameter semantics, but the core action is clear. The 'real Chrome session' detail adds valuable operational context.

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%, and the description does not explain either parameter. It mentions searching with Sogou but gives no meaning for 'keyword' or 'limit'. While 'keyword' is somewhat obvious, 'limit' is entirely undocumented, leaving the agent to guess how result counts are capped.

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 uses a specific verb "Search" with a clear resource "the public web with Sogou", immediately distinguishing it from sibling search engines like Google or Bing. The added detail "through the user's real Chrome session" further clarifies the unique execution context.

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 clearly implies when to use this tool: whenever a Sogou search is required. However, it does not explicitly mention alternatives or exclusions, though the sibling list makes it evident that other search tools exist for different engines. This meets the 'clear context, no exclusions' level.

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