get_daily_summary

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

No annotations exist, so the description must disclose behavior. It specifies the exact data returned (temperature, precipitation, wind gust) and the station identifier, which adds transparency. However, it does not mention data availability guarantees or any quirks.

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 that is concise and front-loaded with the key verb and resource. No extraneous 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 the simple schema (1 optional param), no output schema, and no annotations, the description is reasonably complete. It covers what data is returned and the time range. Could mention that data is from a specific station, but it already does.

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 100%, so baseline is 3. The description adds context by stating 'up to the last 7 days' but does not elaborate on the default behavior (default 7 days) beyond what the schema says.

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 the verb 'Get' and specific resource: daily high/low/avg temperature, precipitation, and wind gust for a specific station. It includes the station ID and the time range (up to 7 days). This differentiates it from siblings like get_current_conditions (current) and get_hourly_history (hourly).

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 for historical daily summaries, but provides no explicit guidance on when to use this vs. alternatives like get_hourly_history. No mention of when not to use it or limitations beyond the 7-day max.

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