check_grass_conditions

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

Discloses side effects: outbound HTTPS to ip-api.com and open-meteo.com, caching, latency 200-600ms, and that it never mutates streak fields. This adds value beyond annotations (readOnlyHint, idempotentHint) which already indicate safe behavior. No contradiction with annotations.

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?

Description is concise, well-structured, and front-loaded. Every sentence provides value: main output, side effects, latency, usage guidance, and alternatives.

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?

Although there is no output schema, the description details the return fields. Combined with annotations covering safety, the description is complete for a read-only tool with no parameters.

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?

Input schema has 0 parameters, so schema coverage is 100%. Description adds no parameter info, which is acceptable since there are none. Baseline 4 for zero 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 returns the user's outdoor context including city/region, weather, sunset, golden-hour, and streak. It uses specific verbs and lists resources, distinguishing itself from sibling get_stats which is for streak-only without network calls.

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?

Explicitly provides when to use ('once per session before deciding whether to nudge the user outside') and when not to use ('don't poll repeatedly; conditions change on the order of minutes'). References alternative tool get_stats for streak-only data and mentions the SessionStart hook.

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