simulate_sea_level_rise

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

No annotations are provided, so the description carries the full burden. It discloses the data source, streaming from open AWS STAC, lack of credentials, modeling approach, and output formats. It omits potential performance limitations or edge-case behavior, but it provides substantial behavioral context beyond the bare schema.

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 opening sentence is specific and front-loaded, and the Args/Returns structure is easy to parse. The references add credibility but are not strictly operational; still, the description is efficiently organized and not bloated.

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 tool with no schema descriptions and no annotations, the description covers required inputs, optional parameters, return fields, and methodology. It does not mention bbox size limits, processing time, or failure modes, but it is complete enough for correct 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 description coverage is 0%, and the description fully compensates by explaining every parameter: bbox order, water_level_rise_m and storm_surge_m units and defaults, scenario allowed values, and format options. This goes well beyond the sparse schema information.

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 states a specific action: 'Simulate coastal sea-level rise and storm surge inundation using Copernicus DEM GLO-30 and hydrologically connected flood-fill modeling.' It is clear about the resource and method. However, it does not explicitly distinguish this from sibling tools such as assess_location_hazard or analyze_coastal_erosion, so it falls short of a 5.

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 coastal flood simulation with zero-config and EU Floods Directive compliance, and it notes no API keys are required. It does not explicitly state when to use this tool versus alternatives or provide exclusions, so guidance is only implied rather than explicit.

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