env_ocean_temp

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

No annotations provided, so description carries full burden. It does not disclose whether data is real-time, historical, or forecast; any units or output format; or authentication needs. Only states functionality without behavioral traits.

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?

Single sentence with no wasted words. Front-loaded with verb and key information. Highly concise.

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 no output schema and no annotations, the description lacks detail on return format, units, and potential time parameters. However, for a simple point query tool, it adequately covers core purpose. Could be improved with additional context.

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% with clear descriptions for lat and lng (including 'ocean location'). Tool description adds little beyond calling it a 'coordinate'. Baseline 3 is appropriate as parameters are already well-documented.

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?

Clearly states it retrieves sea surface temperature at a coordinate using Open-Meteo marine data. The verb 'Get' and specific resource 'sea surface temperature (SST)' make purpose unambiguous. Distinguished from sibling 'ocean_sst_anomaly' which is for anomalies.

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?

Describes using it to get SST at a coordinate, implying use for a single point, but does not specify when to use versus alternatives like ocean_buoy_data or ocean_chlorophyll, nor when not to use. No explicit guidance on context or limitations.

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