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

No annotations exist, so the description carries the full behavioral burden, yet it discloses only marketing claims. The clause 'UNKNOWN never charged' is the single genuine behavioral fact (billing on indeterminate results), and '100% page-cited' hints at citations, but nothing covers mutation risk, jurisdiction scope, data freshness semantics, or failure modes.

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?

It is a single short sentence, so it is not verbose, but every clause is unverified promotional signal rather than operational information. Nothing is front-loaded that helps an agent decide to call it.

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?

A regulatory look-up tool with 2 required free-text parameters, no annotations, no output schema, and no parameter documentation needs the description to define scope and inputs. The description supplies none of this, leaving the tool effectively uncallable with confidence.

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% across three parameters (jurisdiction, use, zone) and the description adds nothing about their format or meaning. What counts as a valid 'use' string (a category? free text?), and what 'jurisdiction' looks like (US state? county FIPS?), is entirely 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 never states what is being checked: it lists quality metrics ('100% golden accuracy', '100% uptime', 'data as of 2026-10-26') that restate nothing beyond the tool name. An agent can only infer 'check whether a land use is permitted' from the name itself, and the description does nothing to distinguish this from siblings such as check_zoning, check_airspace or spray_check.

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 named anywhere in the text. With 11+ sibling check_* tools, the absence of any routing signal leaves the agent guessing whether this or check_zoning / spray_check / check_license is the right call.

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