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

Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing data provenance ('Every identifier comes from the repositories' own metadata; nothing is generated'), the limits of licence verdicts ('not legal advice'), and the empty-result behavior ('say plainly when the brief is empty'). It also enumerates the backend sources searched, which an agent cannot infer from annotations alone.

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?

Front-loaded with purpose and result shape before source details, and most sentences carry real information. It is dense and long for a single paragraph, and the closing 'why' field explanation edges into output documentation that the output schema already covers, but little is pure filler.

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 an output schema exists and annotations cover the safety profile, the description supplies exactly the missing context: sources queried, provenance guarantees, licence caveats, and empty-brief handling. Nothing an agent needs in order to call this correctly appears to be missing.

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 documents all seven parameters, including the domain enum, keyword guidance and the commercial-demotion behavior. The description reinforces a few of these (keywords for long/non-English questions, domain driving GEO search) but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

Opens with a specific verb+resource and scope ('Find open scientific datasets ... that fit a research question') and immediately names the concrete repositories it queries, which cleanly separates it from siblings like search_papers, find_evidence and find_tools. An agent can tell what this tool returns (a citable Research Data Brief with share link) without opening the schema.

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?

Usage context is implied through the source list and the note that life-science domains also search NCBI GEO, plus the instruction to pass `keywords` when the question is long or non-English. However, it never states when to prefer this tool over search_papers, find_evidence or check_retractions, and gives no explicit when-not conditions, so routing between siblings is left to inference.

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