get_tides

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

With no annotations provided, the description carries full burden. It discloses that the tool returns empty for inland spots and requires spotId from search_spots. However, it does not detail other behavioral aspects like error handling, rate limits, or required permissions.

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 extremely concise, with two focused sentences that front-load the main purpose. No word 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?

For a simple read tool with full parameter coverage and no output schema, the description sufficiently hints at the return values (high/low tide times and heights) and the edge case (inland spots). It lacks explicit return structure but is adequate.

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 input schema fully describes both parameters (spotId and days) with details. The description adds value by stating that spotId must come from search_spots and that tides are only for coastal spots, providing context beyond the schema.

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 states the tool retrieves high/low tide times and heights for a coastal Windfinder spot. It distinguishes from siblings like get_forecast by specifying the requirement of spotId from search_spots and the limitation to coastal spots.

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 explains when to use the tool (for a coastal spot with spotId from search_spots) and when not (inland spots return empty). However, it does not explicitly mention alternative tools for inland spots.

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