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

Beyond the annotations (readOnlyHint, openWorldHint), the description discloses paging semantics ('a full page is usually NOT the whole answer'), the response fields (truncated, matchingRecords, nextOffset), and the offset limit (0 to 1000) with an explicit alternative. It also states the return includes dataset schema and records, adding transparency not available elsewhere.

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 rich but every sentence earns its place: purpose, parameters, paging warning, return structure, and source. It is front-loaded with the core action and efficiently packs needed details without redundancy.

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 complexity (paging, source default, return structure) and the absence of an output schema, the description fully equips an agent to call the tool correctly. It covers paging, limits, source, and what is returned, leaving no critical gap.

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 value by noting defaults (limit default 10, maximum 50) and the paging role of offset, plus the source default to 'longbeach'. This goes beyond the schema's raw descriptions.

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 opens with a specific verb and resource: 'Read one PAGE of records from a public open dataset.' It clearly distinguishes the tool from its siblings by referencing city_datasets for dataset_id and explaining the paging behavior, which sets it apart from dataset-listing tools.

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 explicit context on when to use it (paging through large datasets) and an alternative for deeper paging: 'download the full file from the city portal instead.' It also instructs to use dataset_id from city_datasets, which is a clear prerequisite.

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