get_county_unemployment

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 critical behavioral traits: never seasonally adjusted, no SA/NSA option, default latest-observation behavior, and the meaning of annual_only (M13 rows). This is strong transparency beyond what the schema offers.

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 slightly long but every sentence adds value—purpose, behavioral traits, parameter details, alternative tool, and source. It is front-loaded with the main purpose. The inclusion of source is extra but not wasteful.

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 tool's moderate complexity and presence of an output schema, the description covers usage, parameters, behavior, and alternatives. Edge cases like default dates and annual_only are addressed, making it complete for an agent to invoke correctly.

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 has no descriptions (coverage 0%), so the description compensates fully: explains fips with a concrete example, specifies YYYY-MM format for from_date/to_date, and clarifies annual_only behavior. This is essential semantic info not present in the schema.

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 'Get monthly LAUS unemployment data for a single US county', which specifies the verb, resource, and scope. It distinguishes from sibling tools by explicitly noting 'single county' and pointing to compare_county_unemployment for multi-county comparisons.

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 usage guidance: without dates returns latest, with both dates returns time series, annual_only option for annual averages, and explicitly mentions an alternative tool for comparing multiple counties. This helps the agent choose the correct tool.

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