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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful behavioral trait: the free preview masks company names, which sets expectations about output completeness. However, it says nothing about read-only vs. mutating behavior, rate limits, or why names are masked (paywall), leaving significant behavioral 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?

Two tight sentences with zero filler, and the resource description is front-loaded ahead of the preview caveat. It is efficient, though extremely terse.

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, output-schema-less lookup tool, describing the returned fields and the preview limitation covers a fair amount. But the lone input parameter is unexplained and there is no guidance on scope, so an agent cannot fully invoke it correctly.

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% and the sole parameter (state) is undocumented in both schema and description. The listed fields (company, workers affected, dates) describe output, not the input filter, so the agent gets no guidance on how to scope the query geographically.

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?

Names a specific dataset (WARN Act layoff notices) and enumerates the returned fields (company, workers affected, dates), which is far more informative than its bare name. It does not explicitly differentiate itself from siblings like chandler_court_signals or chandler_signals, so it falls short of a 5.

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 guidance and no mention of alternatives among the chandler_* family. The only contextual clue is a note about the free preview, which is a data caveat rather than usage direction.

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