fetch_dataset

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

With no annotations provided, the description bears the full disclosure burden. It reveals a rate-related behavior (free tier max 10 records per query) and the pathway for higher limits. But it does not disclose response format, error behavior, pagination quirks, or consequences of exceeding the tier quota.

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 two short sentences: the first fronts the main purpose and mechanism, and the second provides the critical free-tier constraint and upgrade path. No words are wasted and the structure supports quick comprehension.

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?

For a 3-parameter tool with full schema coverage, the description supplies the main additional context an agent needs: the free-tier cap and how to get access to more records. The biggest gaps are not suggesting a preceding tool like list_datasets to find dataset names and not outlining the default return shape, but it remains broadly complete enough to call the tool.

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 input schema already describes all three parameters, including the free-tier limit limit and the dataset name example. The description's mention of 'limit/offset' merely restates what the schema already covers, so it adds little semantic value beyond the structured details.

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 states the core operation clearly: 'Query records from a dataset' and identifies the pagination mechanism via limit/offset. This differentiates it from sibling tools such as list_datasets, which lists available datasets rather than records, making the purpose unambiguous.

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 free-tier sentence gives explicit usage context: a query can return at most 10 records unless the user purchases products or tops up credits. However, it does not explicitly say when not to use this tool, nor does it point to a sibling like list_datasets when the dataset name is unknown.

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