datahub_search

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

With no annotations, the description carries full burden. It states the tool returns search results with specific fields and notes price is in USD stablecoin. It also reveals that API listings have per-request pricing and are accessed via gate_fetch, which is important behavioral context. However, it doesn't mention authentication or rate limits.

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 concise (two sentences) and front-loads the main purpose. The second sentence, though slightly run-on, packs useful information about how to handle different result types. Minimal waste.

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 no output schema, the description lists the return fields explicitly. It also covers the two distinct data kinds and their follow-up tools. It does not mention pagination, ordering, or error handling, but for a search tool this is largely sufficient.

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?

Input schema coverage is 100%, so baseline is 3. The description adds value by explaining that the 'limit' parameter defaults to 10 and must be between 1 and 50, and that the 'query' parameter uses plain keywords with no syntax. It also provides usage guidance for different listing kinds, which goes beyond 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 starts with a clear verb+resource ('Search the Solinkify DataHub marketplace') and specifies the return fields (id, title, price, etc.). It further distinguishes between dataset listings (use datahub_buy) and API listings (use gate_fetch), effectively differentiating this tool from sibling tools.

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 explains when to use the tool (to search the marketplace) and how to act on results: buy datasets with datahub_buy, access API listings via gate_fetch. It also clarifies query behavior ('Plain keywords work best; there is no query syntax'). It doesn't explicitly state when not to use it, but the guidance is clear enough.

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