clmtemp

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

No annotations exist, so description bears full burden. It details request and response structure but does not disclose data limits, rate limits, or error handling. While it mentions optional parameters and defaults, behavioral traits like being read-only are implicit but not stated.

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 lengthy due to including response key details and an example. While the example is helpful, the response format section adds bulk. It is front-loaded with purpose but could be more concise without losing essential information.

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, describing response keys is useful for an agent to understand return values. However, it lacks information on data availability, station list references, or error responses. The description is complete for basic usage but not for edge cases or integration 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%, so baseline is 3. Description adds a request example and indicates month is optional, but largely repeats schema information. It provides minimal additional meaning beyond what the schema already captures.

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 'Daily Mean Temperature (CLMTEMP) API Request' and describes the parameters, establishing that it retrieves mean temperature data. However, it does not explicitly differentiate from sibling tools like clmmaxt and clmmin, which could cause confusion.

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 on when to use this tool versus alternatives. There is no mention of, for example, 'Use this for mean temperature; for max use clmmaxt.' The description only lists parameters and response format, lacking context for selection.

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