eudr_render_satellite_map

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says the tool generates output; it does not disclose whether any data is written, whether external services are called, whether results are cached, or what the response looks like. For an unannotated tool, this is a significant gap.

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 a single sentence with no filler and front-loads the action. It is concise, though the combined phrase 'visual multi-spectral satellite imagery metadata and NDVI canopy density radar visualization' could be restructured for clarity.

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?

The schema covers all parameter semantics and the description conveys the core purpose, so an agent can probably select and invoke the tool correctly. However, there is no output schema and the description leaves the return format vague—whether it returns an image, a URL, metadata, or some combination is not clear.

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 100%, so the schema already documents all four parameters including enums and defaults. The description adds only loose thematic context around satellite imagery and NDVI, without meaningful parameter-level detail beyond the schema.

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 names a specific action ('Generates') and resource ('satellite imagery metadata and NDVI canopy density radar visualization') tied to an EUDR plot. It is distinct from the sibling tools, which are clearly not render/visualization tools. However, the phrase 'visual multi-spectral satellite imagery metadata and NDVI canopy density radar visualization' is awkward and leaves the exact deliverable somewhat ambiguous.

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 gives no indication of when to prefer this tool over alternatives such as eudr_check_deforestation or eudr_verify_plot. It does not state prerequisites, exclusions, or conditions under which a different EUDR tool should be used instead.

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