Return WARN Firehose pricing tiers, included tools, and signup URLs.
Use this when the user asks about pricing, hits a rate limit, or wants to upgrade. Returns tier prices, daily call limits, included datasets, and direct signup links so the user can act immediately.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full behavioral disclosure. It frames the tool as read-only ('Return') and enumerates output items, implying no side effects. It could add notes on data freshness or authentication, but the zero-parameter informational nature makes this adequate.
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?
Three sentences, each earning its place: front-loaded purpose, explicit use cases, and a clear list of return content. No redundant or vague 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?
This is a low-complexity tool with no input parameters and no output schema. The description fully covers what it does, when to use it, and what it returns, making it complete for an agent to select and invoke.
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 tool has zero parameters, so the baseline is 4. The description adds context about what the tool returns, which is unnecessary for parameter semantics but harmless. The schema coverage is effectively complete (100%).
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 uses a specific verb, 'Return', and identifies the exact resource: 'WARN Firehose pricing tiers, included tools, and signup URLs.' This clearly distinguishes it from all data-focused sibling 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?
The description explicitly states when to use the tool: 'when the user asks about pricing, hits a rate limit, or wants to upgrade.' It does not mention when not to use it or name alternatives, but the use cases are very clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools overlap in function: get_recent_layoffs, get_state_summary, and search_layoffs all return layoff notices with various filters. get_state_intelligence also overlaps with get_state_summary but adds cross-dataset information. Descriptions help, but an agent may struggle to choose the right tool without careful reading.
Most tools follow a get_verb pattern and use snake_case consistently. A few deviations like authenticate (verb-only), search_layoffs, and export_records are action-oriented but acceptable, making the overall pattern mostly predictable.
With 12 tools, the server is well-scoped for a labor market intelligence API. Each tool serves a distinct purpose, and the count is neither sparse nor overwhelming for the domain.
The tool set covers core workflows: authentication, search, bulk export, state-level intelligence, risk signals, and talent pipeline. Minor gaps exist, such as no company-level cross-dataset view (similar to state_intelligence for a company) and no direct record-by-ID retrieval, but these are workable.