get_daily_min_temperature

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

No annotations are provided, so the description carries the full burden. It only states data retrieval; it does not disclose units, timezone, response format, optional filtering behavior, or any other operational traits. For a tool with no annotation coverage, this is a significant gap.

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, focused sentence with no unnecessary words. It is front-loaded with the action and resource, and is appropriately sized for the tool's simplicity.

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?

Despite having an output schema, the description is too minimal for a tool with 4 parameters (1 required) and no annotations. It omits critical context such as station format, optional filters, and default behavior, leaving the agent underinformed for proper 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?

Schema description coverage is 0%, so the description must compensate. It mentions 'specific station' but does not define station identifier format or explain lang, year, or month parameters. It completely neglects parameter semantics, making it impossible for an agent to construct correct arguments beyond the required station.

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 uses a specific verb+resource: 'Get daily minimum temperature data' and clearly distinguishes from siblings like get_daily_max_temperature and get_daily_mean_temperature. It also adds geographic scope ('Hong Kong') and station-level granularity, making the purpose unmistakable.

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 usage when needing daily minimum temperature for a specific station in Hong Kong, but it does not explicitly contrast with sibling tools (e.g., max/mean/current weather) or state any exclusions. There is no when-to-use vs alternatives guidance beyond the inherent purpose.

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