Read rows of a DataLens dataset

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are paginated (one page per call) and advancing pages requires offset combined with sort, which is a real pagination constraint the agent needs.

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?

Two tight sentences with zero waste. The core scope is front-loaded and the two operative constraints (guid-based columns, offset+sort paging) follow immediately.

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 an 8-parameter read tool with full schema coverage and no output schema, the description covers the two non-obvious behaviors an agent needs (guid naming and pagination coupling). It does not describe the shape of returned rows, which is a minor gap given there is no output schema to lean on.

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%, so the baseline is 3, but the description adds actionable meaning by clarifying that columns are identified by field guid rather than title and by pointing to datasets_get as the source of those guids. This resolves a likely confusion that the raw schema alone does not preempt.

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?

States a concrete verb+resource ('Rows of a dataset') and immediately scopes it to 'the columns asked for, one page per call', which tells the agent this is a paginated row reader, not a metadata fetch. It references the sibling datasets_get for column guids, giving some sibling differentiation, though it doesn't distinguish itself from other data-reading tools like charts_data_get.

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?

Provides real usage guidance for the mechanics (read guids via datasets_get; pass offset together with sort for the next page), but never states when to choose this tool over alternatives such as charts_data_get or sqlqueries_run. Usage context is implied rather than explicitly bounded.

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