climate_data_guide

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

No annotations are present, so the description must convey behavioral traits, but it only states it is a 'guide' and 'DEMO.' It does not disclose whether it retrieves real-time data, returns static text, or has any side effects. The 'DEMO' tag hints at limited functionality but is insufficient.

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 very short (two phrases), which is concise, but it lacks structure and fails to provide essential information. It front-loads the domain but sacrifices completeness for brevity.

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 tool has an output schema (unseen), the description still needs to explain what the tool returns. It does not specify return format or whether it's a list, map, or text. For a guide-like tool with two parameters, more context is needed to use it correctly.

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?

The input schema has two parameters (data_type, county) with no descriptions (0% coverage). The description does not explain what values data_type expects (e.g., 'weather,' 'drought,' 'flood') or how county filters results. Agents have no guidance on parameter usage.

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 mentions 'Kenya climate data sources: weather, drought, flood risk,' which indicates the resource domain and topics. However, it lacks a specific verb (e.g., 'list,' 'query,' 'provide') to define the action the tool performs, making the purpose only moderately clear.

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?

There is no guidance on when to use this tool versus its siblings (e.g., climate_adaptation_guide). The term 'DEMO' may imply it's a demonstration or not production-ready, but this is not clarified. No when/when-not information is provided.

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