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 tool may return UNKNOWN, and UNKNOWN is never charged, so an agent knows a non-answer is possible and costless. However, it discloses nothing about permissions, rate limits, response shape, or what a positive result contains, and the accuracy/uptime statistics are marketing rather than actionable 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?

It is short, but almost the entire sentence is spent on golden-set accuracy, page-citation rate, and 24-hour uptime figures that do not help an agent decide or invoke. The one operational fact (UNKNOWN, no charge) is buried mid-sentence rather than front-loaded.

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 six-parameter, required-field domain-check tool with no output schema and no annotations, the description supplies neither the purpose, nor the parameters, nor the return contract. It is essentially unusable for correct invocation beyond guessing from the name.

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?

Six parameters at 0% schema description coverage, and the description mentions none of them — parcel, address, district, latitude, longitude, jurisdiction are entirely unexplained. It does not even note that jurisdiction is required or how to choose between address-based and coordinate-based lookup.

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 the tool actually checks — it only restates the tool name and piles on provenance/uptime/accuracy claims. An agent learns that a 'solar siting check' exists and is free in beta, but not that it evaluates whether a parcel is suitable for solar development, nor how that differs from get_zoning or check_use_allowed.

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 guidance at all, despite siblings like get_zoning, check_use_allowed, check_coverage, and get_site_report that clearly overlap. The only routing-adjacent statement is that it returns UNKNOWN for free while unwired, which is a caveat, not usage guidance.

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