nhgis_search_time_series_tables

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

No annotations are provided, so the description carries the full burden. It discloses that the tool internally fetches all ~400 time series tables and then filters by keyword, which is a useful behavioral detail. However, it does not mention performance implications, return structure, or error cases, so it's informative but not exhaustive.

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 sentences, front-loaded with the purpose and a supporting clarification. Every sentence adds value, with no wasted words.

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 low complexity (1 parameter) and lack of output schema, the description adequately explains the tool's operation and the nature of time series tables. It doesn't specify the exact return format, but it's sufficient for a search tool. Some might want more detail, but it's largely complete.

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 schema description covers the keyword parameter fully with case-insensitive matching explanation. The tool description adds the phrase 'name or description' but that essentially mirrors the schema. With 100% coverage, the baseline is 3, and the description adds minimal extra value.

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 clearly states 'Search NHGIS time series tables by keyword' with a specific verb and resource. It distinguishes from sibling tools like list (which likely returns all) and get (which fetches a specific table) by focusing on keyword-based filtering.

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 implies a use case (searching with a keyword) but does not explicitly compare to alternatives such as nhgis_list_time_series_tables or nhgis_get_time_series_table. It does not state when to use this tool instead of others, so while the context is clear, exclusions or alternative references are missing.

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