Export Result Preview

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

With no annotations, the description must convey behavioral traits. It communicates that the tool is non-destructive ('without writing files') and output is bounded. However, it omits details like whether the tool is idempotent, success/error states, or any authentication requirements. The provided traits are useful but incomplete.

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, front-loaded sentence that conveys all essential information without waste. Every word is purposeful and contributes to understanding the tool's core function.

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 has 5 parameters (including complex ones like columns and profile) and no output schema or annotations, the description is too sparse. It fails to clarify input requirements (e.g., row structure, column definitions) or output format expectations, leaving the agent under-informed.

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%, so the description should compensate by explaining parameter purposes. It only mentions 'Markdown or CSV preview string' and 'bounded', leaving parameters like columns, maxRows, and profile unexplained. The agent cannot infer how to correctly set these parameters without additional knowledge.

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 verb 'Generate', the resource 'Markdown or CSV preview string', and the context 'from already returned rows without writing files'. It effectively distinguishes this tool from siblings like ob_query (which fetches rows) and ob_summarize_result (which summarizes rows).

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 implies when to use this tool: when rows are already available and a lightweight text preview is needed without writing files. It does not explicitly exclude specific alternatives, but the context of siblings like ob_query_preview or ob_compare_query_results is sufficiently differentiated by the 'without writing files' clause.

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