base_tablePreview

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

Description discloses read-only sampling behavior and persist option for materialization, adding context beyond annotations (readOnlyHint, idempotentHint). Does not contradict annotations.

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?

Description is front-loaded with purpose, then usage, then parameters. Well-organized but slightly verbose; could be more concise while retaining key info.

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?

No output schema, but description covers use cases, arguments, and behavioral aspects. Lacks details on return format (e.g., JSON structure), but adequate for a preview 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 coverage is 100% and description repeats but clarifies parameters (e.g., table_name, database_name, persist). Adds value by explaining purpose beyond schema definitions.

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 tool returns a quick sample of first few rows from a table/view without SQL. It distinguishes from sibling base_readQuery by specifying when not to use (WHERE clause, filter, SQL).

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 when to use (explore/peek without conditions) and when not to use (user provides WHERE clause, filter, or SQL), and suggests alternative base_readQuery.

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