stata_data_rows

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

No annotations are provided, so the description carries the full behavioral burden. It correctly implies a read-only retrieval and specifies the output shape, but it does not disclose what happens when no dataset is loaded, whether session state is affected, or how errors are surfaced.

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 compact sentence that front-loads the action, target resource, and return format. Every part contributes useful information, with no filler or redundant repetition of the tool name.

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?

For a simple read-only row-fetching tool, the description covers the essential purpose and return format, while the schema covers parameters. It does not mention prerequisites such as having a dataset loaded or error behavior, but these are minor for a tool of this simplicity.

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?

The input schema documents both parameters fully, including constraints, defaults, and meaning (rows 1-50 default 10, session_id defaults to 'default'). The description adds no additional parameter semantics, so the schema-based baseline of 3 is appropriate.

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?

Description states a specific verb (返回) and resource (当前数据集前 N 行), and even clarifies the return format as a structured two-dimensional array. It is clear about what the tool does, though it does not explicitly differentiate it from sibling tools like stata_inspect_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 phrase '供 agent 直接查看数据' implies this is the tool to use when the agent needs to view the dataset rows directly. However, there is no explicit guidance about when to choose this tool over alternatives, nor any exclusions or prerequisites.

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