Get Tide Predictions

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

Discloses that it returns predicted water levels in feet/meters and covers US regions. This adds value beyond annotations (readOnly, idempotent) by specifying data type and geographic scope. However, it does not mention any rate limits or pagination behavior.

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?

Two sentences with no wasted words. Front-loaded with purpose, followed by key details. Excellent conciseness.

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?

Covers purpose, intervals, units, and geography. With output schema present, it does not need to explain return format. Misses guidance on datum options and max 31-day range (though schema covers it). Adequate for the complexity.

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 100%, so baseline is 3. The description adds example station IDs and mentions interval/units, but these are already in the schema. No additional semantic meaning beyond what is in the parameter descriptions.

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 returns tide predictions for NOAA stations, specifying intervals and units. However, it does not differentiate from the sibling tool 'tides.noaa.water_levels', which could lead to confusion about when to use each.

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?

No explicit guidance on when to use this tool versus alternatives like 'tides.noaa.water_levels' or weather tools. The description mentions geographic coverage (US coastlines) but lacks when-to-use and when-not-to-use advice.

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