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

With annotations already declaring readOnlyHint/destructiveHint, the description adds substantial context: a hard 100-row cap with 25 default, offset-based paging, the `has_more`/`next_offset` response contract, cross-workspace access returning 'dataset not found', and that the call is free. These are the behavioral traits annotations cannot express.

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 paging constraint and defaults are front-loaded, and each clause carries information. It is dense for a single paragraph, but no sentence is filler given the 0% schema coverage it has to compensate for.

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 exists, yet the description names the return fields (`has_more`, `next_offset`) and the row shape for each format, plus the cross-workspace failure mode and cost. An agent has everything needed to page correctly and switch formats.

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 must carry all four parameters — and it does: `limit` (max 100, default 25), `offset` (paging), `format` (json row objects vs csv string, with defaults), and `dataset_id` (`ds_…` prefix, error semantics). No parameter is left ambiguous.

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 specific verb and resource ('Read a page of rows from a stored dataset') with the `ds_…` identifier convention, and implicitly distinguishes itself from hyreflow_dataset_export by contrasting csv rows with 'the exported file'. An agent can identify the operation without opening the schema.

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?

Usage is implied by the format discussion (csv = fewer tokens, same cells as the export), steering token-conscious reads toward csv, but there is no explicit statement of when to use this over hyreflow_dataset_export or hyreflow_datasets_list. Adequate but leaves the routing decision to inference.

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