preview_data

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

With no annotations provided, the description carries the full behavioral burden. It does disclose pagination and conditional filtering, and 'preview' weakly implies a read-only nature. However, it omits important behavioral details such as output format, source requirements, default behavior, or whether previews are bounded or sampled.

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 short sentence with no wasted words, and the main behavior is front-loaded. It is appropriately concise, though it may be slightly too terse given the number of parameters and lack of annotations.

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?

The tool has 5 optional parameters, no annotations, 0% parameter documentation, and no guidance on source selection or condition syntax. The description is not complete enough for an agent to confidently invoke the tool with correct parameter values, despite the presence of an output schema.

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% across 5 parameters, so the description must compensate. It adds semantic context for the pagination behavior (page/page_size) and for condition, but says nothing about source or format. Parameter names are somewhat self-explanatory, but the description does not fully clarify their values or intended use.

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 indicates the tool's function with 'preview' as the verb and 'data' as the resource, and adds two distinguishable behaviors: pagination and conditional filtering. It differentiates from siblings like sql_query, aggregate_stats, and data_insights, though it does not specify which data source is being previewed.

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 provides no guidance on when to use this tool versus alternatives such as sql_query, query_video_stats, or data_insights. There is no mention of use cases, prerequisites, or when this tool should not be used.

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