stac_map

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

The description adds behavioral context beyond the readOnlyHint annotation by detailing the map's visual elements (polygons, grouping, popup content). It confirms the tool is read-only and visual, consistent with the annotation.

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?

Three sentences efficiently convey purpose, visual output, and usage prerequisite. No redundant information, but could briefly mention the basemap parameter for completeness without adding much length.

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 the tool has 2 parameters and no output schema, the description covers the main use case and prerequisite. However, it omits the basemap parameter and scene_ids format, leaving gaps for an agent to fully invoke the tool correctly.

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 should compensate. It mentions scene_ids and how to pass them ('pass the scene_ids here') but does not explain the format (e.g., comma-separated or array) nor the basemap parameter. This leaves ambiguity for the agent.

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 visualizes STAC scene search results as a multi-layer footprint map, specifying what appears (bounding-box polygons grouped by collection) and details in popups. This distinguishes it from sibling tools like stac_mosaic or stac_pairs_map.

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 explicitly instructs to run stac_search first and then pass scene_ids, providing a clear prerequisite and usage flow. It implies when to use this tool (after a search) but does not explicitly state when not to use alternatives.

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