search_deepseek

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions a timeout parameter but doesn't explain what happens when timeout is reached, whether responses are streamed or complete, authentication requirements, rate limits, or what kind of AI assistant functionality is provided. The description is minimal and lacks crucial operational context for an AI tool.

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 concise with only two sentences that directly state the tool's identity and parameter information. Every word serves a purpose with zero redundancy or unnecessary elaboration. It's efficiently front-loaded with the core purpose immediately stated.

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 an AI assistant tool with no annotations and no output schema, the description is inadequate. It doesn't explain what the tool returns (text response, structured data, streaming), error conditions, or how it differs functionally from other AI tools. Given the complexity of AI interactions and rich sibling tool ecosystem, this minimal description leaves too many operational questions unanswered.

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 100%, so the schema already fully documents both parameters. The description adds minimal value by restating parameter names and the timeout default, but doesn't provide additional semantic context about query formatting, timeout implications, or practical usage examples beyond what's in the schema descriptions.

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's purpose as 'DeepSeek AI assistant' which identifies the specific AI service being accessed. It distinguishes itself from sibling tools like search_chatgpt and search_claude by naming the specific AI model. However, it doesn't specify the exact action (e.g., 'query' or 'chat with') beyond 'assistant', making it slightly less specific than ideal.

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 provides no guidance on when to use this tool versus the many alternative AI/search tools in the sibling list. There's no mention of DeepSeek's specific capabilities, strengths, or appropriate use cases compared to ChatGPT, Claude, Gemini, or search engines like Google or Bing. The agent must infer usage context from the tool name alone.

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