oceanforecastOcean forecast — current, wave height, sea temperature.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | Yes | ||
| lon | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Feature type (GeoJSON) | |
| geometry | No | ||
| properties | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world. The description adds the specific output variables (current, wave height, sea temperature) but no further behavioral context such as rate limits, authentication, or data source reliability. No contradiction exists.
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, front-loaded sentence with no filler words. It is appropriately sized for a simple tool, but the brevity contributes to under-specification of parameters and usage context.
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?
Given the tool's simplicity and the presence of an output schema, the description is minimally viable. However, it lacks usage guidelines and parameter semantics, and leaves ambiguous terms like 'current' unexplained. It does not fully cover the context an agent would need for correct invocation.
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 lists only lat and lon with no descriptions (0% schema coverage). The description does not mention or explain these parameters, missing the opportunity to clarify units, ranges, or required format. While lat/lon are inherently understandable, the description adds no value 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 it provides an ocean forecast with specific variables (current, wave height, sea temperature). It distinguishes from general forecast tools by focusing on ocean conditions, but the term 'current' is ambiguous and there is no explicit differentiation from sibling tools like 'forecast' or 'nowcast'.
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 guidance is provided on when to use this tool versus alternatives such as 'forecast' or 'nowcast'. The description implies use for marine conditions but does not state prerequisites, exclusions, or comparison to related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but there is some overlap among closely related ones (e.g., ask_pipeworx, ask_pipeworx_grounded, deep_research; multiple Polymarket tools). Descriptions are detailed enough to differentiate, but an agent might still misselect on subtle differences.
Names consistently use lowercase with underscores, but no strong verb_noun pattern. Some are noun-based (airquality, nowcast), others verb-based (ask_pipeworx, compare_entities). This is readable but not perfectly predictable.
35 tools is high but justified by the server's broad scope (data queries, betting analysis, weather, memory, subscriptions). The number feels appropriate given the comprehensive functionality described.
The tool set covers an impressively wide range of capabilities: data querying with multiple modes, entity profiling, comparisons, search, betting analysis, weather, memory, subscriptions, and feedback. Missing features (e.g., updating memories) are minor; the surface is remarkably complete.