ground_truth

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

With no annotations, the description carries the full behavioral burden. It discloses only that the output is 'bundled' and includes one provenance record; it says nothing about permissions, rate limits, determinism, or what the 'five questions' are.

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, but its brevity comes from under-specification rather than efficiency; the front-loaded content is a cryptic noun phrase with no actionable information for an agent.

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 and no output schema, the description must supply everything, and it does not: the nature of the 'five-question answer', what the coordinates select, and the output shape are all absent. For a 2-parameter required tool this is inadequate.

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 coverage is 0% and the description never mentions lat or lon, so it adds no meaning beyond the bare schema property names. It partially compensates only in that lat/lon are conventional and self-explanatory, but the description contributes nothing itself.

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 names an artifact ('five-question answer') and a 'provenance record' but never states a verb or the actual operation, so it reads more like a fragment of the return value than a purpose. It does not distinguish this tool from siblings such as ground_stability or resource_indication, and the term 'five-question answer' is unexplained.

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 statement of when to use this tool, when not to, or how it relates to any of the numerous siblings. The only hint of context is the implicit lat/lon geographic grounding, which is not made explicit.

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