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 the live source is not wired, that calls return UNKNOWN without charge, and that UNKNOWN is never billed; however, it omits operational details such as authorization, rate limits, and what a successful response looks like, and the accuracy/uptime claims are noisy and somewhat inconsistent with the 'not wired' caveat.

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 critical caveat is front-loaded in the opening parenthetical, but the sentence then spends substantial space on golden accuracy, page-citation, uptime, and data-date metrics that do not help an agent decide or invoke correctly. It is compact but not optimally structured for tool selection.

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 two-parameter tool with no output schema and no annotations, the description should explain the return values and parameter meaning. It only says the live source is unwired and currently returns UNKNOWN, leaving the success behavior and coordinate semantics undocumented.

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%, and the description does not mention lat or lon at all. The schema provides types and ranges, but the description adds no meaning about coordinate order, datum, precision, or expected coordinate system.

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 soil data the tool retrieves or what a successful result would contain; it mostly restates the name and adds beta/status metrics. An agent can infer soil lookup from the name and lat/lon parameters, but the description itself does not define the resource or distinguish it from siblings like get_wind or get_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 explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The beta caveat implies it currently returns UNKNOWN, but the description does not say what to do instead or when it would be appropriate to call.

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