Pollinations Think MCP Server

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 mentions 'real-time' and 'current information' which hints at freshness, but doesn't disclose critical traits like rate limits, authentication needs, result format, pagination, error conditions, or whether this is a read-only operation. For a web search tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 appropriately sized with two concise sentences that directly state the tool's function and scope. It's front-loaded with the core purpose and avoids unnecessary details. However, the second sentence could be more tightly integrated with the first for slightly better flow.

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 complexity (web search with potential for varied results) and the lack of both annotations and an output schema, the description is insufficiently complete. It doesn't explain what the return values look like (e.g., list of links, summaries), error handling, or operational constraints like rate limits. For a tool that interacts with external APIs and returns unstructured data, more context is needed.

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 input schema has 100% description coverage, with the single parameter 'query' fully documented in the schema. The description adds no additional parameter semantics beyond what the schema provides—it doesn't explain query formatting, length limits, or special syntax. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 with specific verbs ('perform real-time web search') and resource ('using SearchGPT'), and distinguishes it from sibling tools like 'continue_thinking' and 'think' by focusing on external information retrieval rather than internal reasoning. However, it doesn't explicitly differentiate from potential alternative search tools that might exist in other contexts.

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 alternatives. It mentions 'returns current information from the internet on any topic' which implies a broad use case, but offers no explicit when/when-not instructions, prerequisites, or comparisons to sibling tools like 'continue_thinking' and 'think' that might handle different types of queries.

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