landis_soilscapes_point

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds no behavioral detail beyond the return content; mentioning 'caveats' hints at the nature of the result but does not describe side effects, failures, or operational constraints. No contradiction with annotations.

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?

A single front-loaded sentence with no filler. Every element—resource, output, input format—earns its place, and the essential 'WGS84 point' qualification is included.

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 two-parameter point lookup with safe/idempotent annotations and an existing output schema, the description covers what the tool does and what input it expects. Minor gaps such as geographic coverage limitations or out-of-range coordinate handling are not stated, but they are not critical for invocation.

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%, so the description must compensate. It adds the essential coordinate reference system (WGS84) and clarifies that lat/lon represent a single point. The self-descriptive parameter names plus this CRS context provide enough meaning for correct invocation, though the description could additionally state value ranges.

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 states a specific verb ('Return'), a specific resource ('LandIS Soilscapes class and caveats'), and a specific input modality ('WGS84 point'). This clearly distinguishes it from the sibling landis_soilscapes_area_summary, which is the area-based counterpart.

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?

The input condition 'for a WGS84 point' makes the use case clear and implies a single-point lookup as opposed to area summaries. However, it does not explicitly name alternatives or state when not to use the tool, leaving the routing decision partially to the agent.

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