Hourly Weather Forecast

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint. The description adds that it returns temperature and weather conditions for upcoming hours, which is useful but does not go beyond the annotation-provided safety profile or disclose additional behavioral traits like rate limits or data volatility.

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 two concise sentences, front-loaded with the action verb and resource, containing no unnecessary words or 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?

For a parameterless tool with annotations and no output schema, the description adequately explains what the tool returns (temperature and weather conditions) and for what time range (upcoming hours) – sufficient for an AI agent to understand its function.

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?

With zero parameters and 100% schema coverage (trivially), the description does not need to add parameter info. It does not introduce implicit parameters; 'at Homey's location' is not a parameter. A score of 4 reflects the baseline for no parameters.

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 the tool retrieves hourly weather forecast at Homey's location, specifying the verb (get) and resource (hourly weather forecast), and distinguishes itself from sibling 'get_weather' which likely provides daily or current data.

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 hourly forecasts but provides no explicit guidance on when to use this versus alternatives like 'get_weather', nor any when-not instructions. Context implies its purpose but lacks explicit guidelines.

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