get_regional_turnover

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

The description indicates a read-only getter and provides a parameter constraint, but offers no additional behavioral context such as data frequency, source, update cadence, or required permissions. Since there are no annotations, the description carries the full burden and falls short of disclosing potential quirks or limitations.

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 short sentences, front-loaded with the core purpose and immediately followed by the most critical parameter constraint. No wasted words or redundant information.

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 regional data fetch, the description covers the required parameter but omits details about optional date parameters and the meaning of 'adjustment'. The presence of an output schema mitigates return-format concerns, but the optional parameters remain under-specified, leaving moderate gaps in overall completeness.

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 description adds explicit valid values for the 'region' parameter, which the schema does not provide. However, it leaves 'to_date', 'from_date', and 'adjustment' without any explanation, only partially compensating for the schema's lack of descriptions. The provided enum-like info is valuable but not comprehensive.

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 the action ('Get') and the resource ('regional labor market turnover data'), and specifies the scope ('one of the 4 Census regions'). This distinguishes it from sibling tools like get_state_turnover and get_industry_turnover which target different geographic or industry granularities.

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 the tool is for Census-region-level data but does not explicitly contrast it with state-level or industry-level alternatives. There is no 'use when' or 'instead of' guidance, leaving the agent to infer the appropriate context from the region parameter.

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