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

Adds meaningful context beyond the annotations: explicit nulls when unavailable, source status, timestamp, freshness metadata, and unit/direction conventions. Safety behavior is already covered by annotations, so the remaining gap is minor.

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?

Front-loads the core purpose and stays compact. Some unit clarifications about water temperature, visibility, and current sign are tangential for a wind tool and slightly dilute focus.

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 return metadata, null behavior, units, and freshness reasonably well for a tool without an output schema. However, it leaves the only input parameter poorly specified, which is a notable gap for a forecast 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?

Schema description coverage is 0%, and the nested query object is not explained. The description only hints at 'spot' and 'next hours' without clarifying spot format, the hours default/range, or the query wrapper.

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 a specific resource, wind and gusts, for a verified spot over the next hours. It is clearly distinct from wave/current/temperature siblings by resource, though it does not explicitly name alternatives or exclusions.

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 implies a forecast use case but gives no explicit when-to-use guidance, no exclusions, and no comparison to siblings such as get_forecast, get_conditions, or get_waves.

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