get_area_image

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

The description reveals key behavior: it saves a file to 'outputs/' and returns a path. It also explains that static data ignores the date. No annotations are provided, so the description carries the burden, and it sufficiently covers basic behavior, though it lacks details on overwrite behavior or permissions.

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 extremely concise with two sentences. The first sentence states the core purpose, and the second details parameter formats. Every word adds value, with no 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?

Given no output schema or annotations, the description is minimal but covers basic functionality and parameter formats. It lacks details on the return structure (only 'save path etc.'), error handling, and any additional constraints, making it complete enough for simple use but not comprehensive.

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 0% schema description coverage, the description adds meaning for two of three parameters: it defines 'bbox' format as [min_lon, min_lat, max_lon, max_lat] and 'date' format as YYYY-MM-DD. However, 'dataset_id' is not explained, reducing the overall semantic contribution.

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 it saves a PNG of a specified area and date to 'outputs/' and returns the save path. This distinguishes it from sibling tools like get_dataset_info, get_point_timeseries, and list_datasets, which do not involve image generation.

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 provides context on when to use the tool (when needing an area image) and notes that static data ignores the date, guiding usage. However, it does not explicitly state when not to use it or provide alternatives.

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