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

No annotations are provided, and the description does not disclose side effects, data source, update frequency, read-only status, or any limitations. The tool appears to be a query/index operation, but this is not explicitly stated.

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 description is a single, concise sentence with no redundant or irrelevant content. It efficiently communicates the tool's purpose and key data categories.

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?

The description gives a high-level summary of output content but lacks essential context for a caller: parameter semantics, input expectations, output format, and any usage prerequisites. Without this, an agent cannot reliably invoke the tool.

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?

The schema parameters (date, limit, place) have no descriptions, and the description only loosely implies the 'place' parameter via 'diving area'. There is no explanation of accepted formats, units, defaults, or required combinations.

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 clearly identifies the tool as a Korea scuba index and specifies the content areas (diving area, water temperature, wave height, current speed, tide, comprehensive assessment). It is sufficiently distinct from the sibling beach/fishing/surfing indices.

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 description does not state when to use this tool versus the sibling index tools, nor does it provide any conditions or scenarios for invocation. Usage must be inferred entirely from the tool name and content summary.

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