volcanoes

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

No annotations are provided, so the description carries the full burden. It discloses the data provenance and that this is a catalog of Holocene (not currently active) volcanoes, which is genuinely useful context. However, it says nothing about whether it returns the whole ~1,300-record global list, any pagination, response size limits, or whether values are static reference data versus live.

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 that names source, scope and payload with zero filler. It is arguably over-terse given the missing parameter and usage context, but nothing present is wasted.

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?

An output schema exists, so return values needn't be explained, and the domain is clear. Still, for a tool with a formatting parameter and potentially a very large catalog response, the absence of both parameter meaning and any sense of result volume leaves real gaps.

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?

There is one parameter ('detail', default 'short') with 0% schema description coverage, and the description never mentions it. The agent must guess that other values (e.g., 'full'/'long') exist and what additional fields they unlock — a meaningful gap for a tool whose only knob changes output shape.

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?

States the specific resource and authoritative source (Smithsonian GVP Holocene volcanoes) and enumerates the fields returned (location, type, elevation, last eruption year). The verb is only implied ('returns'), and no sibling is named, but the resource is unambiguous and no sibling in the list covers volcanology, so an agent can recognize the domain instantly.

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 versus alternatives — not even an implicit pointer to quakes_near or disaster_alerts for related hazard queries. It also fails to say when it should not be used (e.g., for live eruption alerts versus the static Holocene catalog).

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