datasets_read

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

With no annotations, the description must carry the full behavioral burden. It states 'Read' and 'preview', implying non-destructive reads, but fails to disclose authentication requirements (e.g., secret needed for private datasets), potential errors, or rate limits. The behavior beyond the stated parameters remains opaque.

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, concise sentence that front-loads the action ('Read dataset contents') and specifies the output scope. Every word is purposeful with no redundancy or extraneous information.

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 tool complexity (3 parameters, no output schema), the description adequately indicates the task but does not specify the return format (e.g., whether it returns rows as JSON, types as list) or pagination. Without annotations, more contextual completeness would be beneficial for correct agent invocation.

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 100%, with each parameter (uuid, secret, rows) having a description. The description adds 'preview rows, columns, and types' but does not elaborate on parameter semantics beyond what the schema already provides. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Read dataset contents — preview rows, columns, and types' provides a specific verb ('read') and resource ('dataset contents'), clearly distinguishing it from siblings like datasets_download (download), datasets_list (list metadata), and datasets_update (modify). It conveys the core functionality of previewing structure and sample 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 offers no explicit guidance on when to use this tool versus alternatives such as datasets_download or datasets_list. The phrase 'preview rows, columns, and types' implies inspection, but there is no mention of when not to use it or which sibling to choose for full downloads or metadata listing.

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