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

No annotations exist, so the description carries the full burden. It does add genuine behavioral facts — calls are currently uncharged and return UNKNOWN because the live source is not wired — but it omits auth requirements, rate limits, what a successful (non-UNKNOWN) response contains, and what the accuracy claims mean operationally.

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 opening repeats the tool name verbatim before any substance, and the bulk of the sentence is operational bragging (78/78 golden accuracy, 100% uptime, data as of a date) that does not help the agent decide or invoke. The one useful fact — returns UNKNOWN, not charged — is buried mid-parenthetical.

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 no annotations, no output schema, and two undocumented parameters, the description needed to explain the resource being checked, the meaning of each parameter, and the shape of a real response. It supplies none of these, so an agent cannot reliably call this tool beyond passing an arbitrary jurisdiction string.

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 0% for both parameters. The description says nothing about what 'jurisdiction' expects (state code? full name? country?) or what 'data_kind' selects among, leaving the agent to guess on a required argument.

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 text largely restates the tool name and then pivots to status/marketing metadata (BETA, free, uptime, golden accuracy). It never states what a state registration check actually determines, what entity or subject it applies to, or how it differs from siblings like check_license or check_zoning.

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 comparison to the many adjacent compliance tools (check_license, check_zoning, check_use_allowed, solar_siting_check). The only usage-relevant signal is that calls are currently free and return UNKNOWN, which tells the agent about cost but not about appropriateness.

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