preview

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

With readOnlyHint already declaring a safe read, the description still adds real behavior: no credentials are transmitted, the 20-row cap, and the return payload shape (access_kind, columns/rows, total or access instructions). The row cap is stated loosely versus the schema's unconstrained n/default 5, but it is not contradictory.

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-loads the action and return shape, which is good, but the same content is duplicated verbatim in Korean and English, roughly doubling length without adding information. Still scannable and free of tangential content.

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?

An output schema exists, so return-value documentation is a bonus rather than a requirement, and annotations cover the safety profile. What remains missing is guidance on dataset_id semantics and how preview relates to show/search, leaving a modest gap for a two-parameter read 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?

Schema description coverage is 0% for two parameters, so the description must compensate. It hints at the row limit ("up to 20 rows") for n, but gives no meaning, format, or expectations for the required dataset_id, leaving the most important parameter undocumented.

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?

States a specific verb and resource (preview the first rows and access instructions from a remote server) and names the scope cap (up to 20 rows). It also distinguishes itself from fetch/get, which sibling-aware agents can use to separate preview-only reads from authenticated retrieval.

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?

Explicitly says credentialed/authenticated queries should go to fetch/get, and that nothing is applied or saved (routing away from the apply sibling). It does not address when to pick preview over show/search/fields, so it stops short of full when/when-not coverage.

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