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

With no annotations, the description carries the full behavioral burden. It usefully discloses that output is tier-gated (a free subset vs a paid full result), which is genuine behavioral context, but it omits auth/subscription mechanics, how the paid tier is unlocked, and any rate-limit or error behavior.

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?

Two compact sentences with the core framing front-loaded and no filler. The branding prefix and pricing detail are slightly marketing-flavored but still carry information and do not bloat the definition.

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 tool with two undocumented parameters, no annotations, and no output schema, the description is incomplete: it neither explains the inputs nor clarifies the shape of returned data beyond a tier listing. An agent cannot confidently call it or interpret results from this text alone.

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 0% for the two parameters (limit, state), so the description must compensate and does not. It mentions 'county name' (an output field, not a parameter) but never explains state or limit, leaving both inputs undocumented.

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 names a resource (county demand-intelligence for local service businesses) but never states a verb or the actual operation the tool performs. It reads more like a product/pricing blurb than a definition of what the call does, leaving the agent to infer that it retrieves county-level signals.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The free/paid tier split describes output content, not when to select this tool over siblings like chandler_warn or chandler_economic_context, so selection is left entirely to inference.

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