nhgis_list_time_series_tables

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context about the temporal and geographic consistency of the tables, but it does not disclose pagination behavior, whether truly all tables are returned in a single call, or the output format. This is a minimal but not comprehensive disclosure.

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 two concise sentences: the first states the primary action and the second provides meaningful context. There is no redundancy or wasted wording.

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 listing tool with only pagination parameters and no output schema, the description provides adequate context: it explains what the tool lists and characterizes the nature of time series tables. It could mention pagination caveats, but the overall intent and scope are clear.

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 already provides descriptions for both parameters ('Results per page' and 'Page number (1-based)'), covering 100% of parameter semantics. The description adds no additional parameter information, so the baseline score 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?

The description begins with a specific action: 'List all available NHGIS time series tables.' It clearly identifies the resource (time series tables) and distinguishes it from sibling tools like nhgis_list_data_tables by emphasizing the multi-year, consistent-geography nature of these tables.

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 gives context that these tables span multiple census years with consistent geographic definitions, which hints at when this tool is appropriate. However, it does not explicitly mention when to use this tool versus alternatives such as nhgis_search_time_series_tables or nhgis_list_data_tables, nor does it state any exclusions.

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