weather_satellite_window

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

No annotations exist. The description mentions 'low cloud cover periods' but does not disclose algorithm, data source, forecast vs. historical, or what defines 'optimal'. Basic transparency but lacks depth.

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 of 15 words, front-loaded with the core purpose. Every word adds value; no redundancy. Highly concise.

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?

No output schema and no description of return format. The tool likely returns optimal windows, but the description neither specifies data structure nor dimensions. Adequate for simple use but incomplete for precise invocation.

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 coverage is 100%, with clear descriptions for lat, lng, and days. The description adds context about 'low cloud cover' but does not significantly enhance parameter understanding beyond the schema. Baseline of 3 is appropriate.

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 'Find optimal satellite imaging windows' with specific focus on 'low cloud cover periods' and scope 'for a location over the next N days'. It uses a specific verb and resource, and distinguishes from sibling weather tools that provide current conditions or forecasts.

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?

No explicit guidance on when to use this tool vs. alternatives like sentinel_search or landsat_metadata. The description implies usage for planning satellite captures but does not provide when-not-to-use or reference siblings.

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