Economic Census Tool

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, which the description aligns with and adds context about the tool's comprehensive and detailed scope. No contradictions; description supplements annotations with qualitative claims about being the most detailed source.

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 sentences, front-loading the core purpose and data types in the first sentence and highlighting significance in the second. Every word adds value with no redundancy or unnecessary detail.

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?

The description covers what the tool does, what data it returns, and the census periodicity. Given no output schema, it could briefly mention that results are tabular or geo-coded, but overall it is complete enough for a data retrieval tool with no required parameters.

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 description coverage is 100% with detailed descriptions for each parameter. The tool description adds no semantic information beyond what the schema provides, such as examples of NAICS codes or variable abbreviations already documented in schema descriptions.

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 retrieves comprehensive business statistics from the Economic Census (every 5 years), including specific data types like establishments, employment, sales, payroll, and value added. It distinguishes from sibling tools like the annual business survey by emphasizing the census's comprehensive and detailed nature.

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 use for detailed business economy facts but does not explicitly state when to use this tool versus alternatives like the annual business survey or county business patterns tool. No direct comparison or exclusion criteria are provided.

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