get_weather

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

无注释，描述未提及任何副作用、依赖或限制（如API密钥、数据来源）。描述仅概括功能，未披露行为细节。

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?

描述简短，无冗余信息，结构清晰。

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?

无输出schema，描述未说明返回数据格式（如JSON结构），也未提及可能的错误情况。整体信息量不足。

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?

参数列表简单，但描述未解释每个参数的含义、格式或默认值的影响。例如，temperature_unit的可能值未说明。

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?

描述明确说明了工具的功能（获取当前天气和预报），但未指定返回值格式或用途。与兄弟工具（如搜索位置、天气仪表盘）的区分度一般。

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?

未说明何时使用此工具与何时使用其他工具（如天气仪表盘），也未提供任何使用前提或限制。

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