sg_dataset_search

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

No annotations are provided, so the description itself must convey behavioral traits. It states that the tool returns known dataset IDs and browse links, which implicitly defines the output and hints at a limitation: only 'known' datasets. No mention of pagination, rate limits, or auth is made, but as a read-only search tool this is less critical. The description adds useful context beyond a simple verb.

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 a single sentence that packs the purpose and output type, with no fluff.

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 simple nature of the tool (one parameter, no output schema) and the absence of annotations, the description covers the purpose and return value adequately. It could mention how results are ordered or paginated, but that may be outside the essential scope.

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 schema already fully documents the single query parameter with examples. The description does not add extra semantic meaning beyond restating that the tool searches for datasets, so the baseline of 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?

The description uses the specific verb 'Search', names the resource 'Singapore government datasets on data.gov.sg', and specifies the return value (dataset IDs and browse links). This clearly distinguishes it from sibling tools like sg_dataset_fetch, which retrieve specific datasets, or sg_weather, which provides specific data.

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 that this is for finding dataset IDs and links, which could then be used with sg_dataset_fetch, but it does not explicitly state this workflow or any exclusions. No alternative tools are mentioned, leaving some ambiguity about when to use this versus searching directly on the website.

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