search_datasetsSearch public-safe Dynamik dataset metadata. Results declare release availability and do not imply account entitlement.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No |
| Name | Required | Description | Default |
|---|---|---|---|
| datasets | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: results are public-safe, indicate release availability, and do not imply account entitlement. This helps set expectations without contradicting annotations.
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?
Two short sentences with no filler. The primary action and key qualification are front-loaded, and the entitlement caveat earns its place by preventing incorrect interpretation of results.
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 a simple optional query, strong safety annotations, and an existing output schema, the description covers the essential behavioral aspects. The main missing element is routing guidance relative to sibling tools, but this is not critical for a straightforward metadata search.
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 what 'query' means beyond the implicit search context. It does not state whether query is free-text, supports exact names, or accepts partial matches. With only one optional parameter, the gap is modest but still present.
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') and resource ('Dynamik dataset metadata'), clearly distinguishing it from the sibling describe/get tools. It also adds a useful qualifier ('public-safe') that clarifies scope immediately.
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 implies this is the tool for searching metadata, but it does not explicitly state when to use it instead of describe_dataset, describe_dynamik, or get_dataset_sample_link. There is no when-not guidance or mention of alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a clearly distinct function: describing a dataset, describing the Dynamik platform, searching catalog metadata, and generating a sample link. There is no meaningful overlap between them, and the shared 'describe' prefix is disambiguated by its object.
All tool names follow a consistent snake_case verb_noun pattern, with verbs like describe, get, and search paired with clear objects. The naming style is uniform and predictable across the entire set.
Four tools is well-suited to the server's focused purpose of exposing public dataset metadata and onboarding information. Each tool earns its place without redundancy or bloat.
The set covers search, detailed metadata inspection, sample link generation, and platform context, which is sufficient for a public-safe metadata layer. The only minor gap is a lack of full dataset content access, but that appears intentional given the server's explicit public-safe, non-proxy scope.