get_demographics

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what data is returned (age, race, income demographics) and the data source (American Community Survey), which is helpful. However, it doesn't describe important behavioral traits like whether this is a read-only operation (implied but not stated), potential rate limits, authentication requirements, error conditions, or how county-level data differs from state-level. The description adds some context but leaves significant gaps.

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 well-structured and appropriately sized. It starts with a clear purpose statement, then provides parameter details in a labeled 'Args' section, and concludes with return value information. Every sentence adds value: the first establishes scope, the parameter explanations are essential given schema gaps, and the return statement clarifies output content. 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 tool's moderate complexity (2 parameters, US geographic focus), no annotations, and the presence of an output schema (which handles return value documentation), the description is reasonably complete. It covers purpose, parameter semantics, and output content adequately. The main gap is lack of behavioral context like rate limits or error handling, but the output schema reduces the need for detailed return value explanation.

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 substantial value beyond the input schema, which has 0% description coverage. It explains that 'state' requires a 'Two-letter state code' with examples ('CA', 'TX'), and 'county' is a 'FIPS code (3 digits)' and optional. This provides crucial semantic context that the bare schema lacks. The only minor gap is not clarifying if county codes are state-specific or national.

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 tool's purpose: 'Get demographic breakdown for a US state or county' with specific data sources (American Community Survey) and demographic categories (age, race, income). It distinguishes from siblings like 'get_population' or 'query_census' by focusing on detailed demographic breakdowns rather than general population counts or census queries. However, it doesn't explicitly contrast with all similar tools like 'get_housing_stats' which might overlap in socioeconomic data.

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 usage context through the parameter descriptions (US state/county focus) and return data specification, suggesting it's for detailed demographic analysis rather than broader geographic or non-US queries. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get_population' for basic counts or 'query_census' for raw census data, and doesn't mention prerequisites or exclusions.

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