sg_dataset_fetch

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

Since no annotations are provided, the description carries the full burden. It only states that fetching, sorting, and full-text search are supported. It does not disclose response format, pagination behavior, error handling, rate limits, or other behavioral traits.

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, front-loaded with the core action and key features. No wasted words or redundant restatements of the tool name.

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?

There is no output schema and no annotations, so the description must clarify what the agent can expect. It does not mention return value structure, pagination, or limits. For a data-fetch tool this is a significant gap, though the core operation is clear.

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 coverage is 60%, with dataset_id, sort, and search described. The description adds 'supports sorting and full-text search,' which maps to the sort and search params but offers no new syntax or behavior. limit and offset have defaults but are undocumented in both schema and description.

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 action ('Fetch rows from a data.gov.sg dataset by resource ID') and its key capabilities (sorting and full-text search). This distinguishes it from sibling tools like sg_dataset_search, which is about searching for datasets rather than retrieving rows.

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 usage when you have a dataset ID and need rows, with optional sort/search. However, it does not explicitly mention when not to use it or point to alternatives like sg_dataset_search for dataset discovery.

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