Annual Business Survey Tool

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds context about the survey replacing the SBO and annual data availability (2017-present), which is consistent. It does not mention response size, rate limits, or pagination, but for a read-only tool with thorough annotations, this level of additional transparency is 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?

The description is a concise three-sentence paragraph that front-loads the main verb 'Retrieve' and efficiently covers source, data types, demographics, and temporal scope. It avoids redundancy and earns each sentence's place, though breaking into sub-topics could improve scannability.

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?

With 9 parameters, no output schema, and moderate complexity, the description covers the tool's purpose, data source, and key demographics but lacks specifics on output format (e.g., JSON structure, pagination) or handling of multiple variables. It meets basic needs but leaves gaps in understanding the exact result shape.

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 coverage is 100%, so the baseline is 3. The description adds overarching context about the survey and demographics but does not explain parameter syntax or relationships beyond what the schema already provides. It reiterates variable names and owner demographics, which aligns with schema descriptions but adds minimal new semantic 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 it retrieves business ownership data from the Annual Business Survey (ABS), specifies demographics (sex, ethnicity, race, veteran status), and lists data types (employer firms, employees, payroll, receipts). It distinguishes from the replaced SBO and provides temporal context (2017-present), effectively differentiating it from sibling tools like county_business_patterns_tool or economic_census_tool.

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 mentions it is 'useful for analyzing business ownership patterns, diversity in entrepreneurship, and economic contributions by demographic groups,' implying usage context. However, it lacks explicit guidance on when not to use it or alternatives among siblings, leaving the agent to infer usage boundaries without clear exclusion criteria.

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