eudr_satellite_mine_audit

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

With no annotations, the description carries the full burden. It usefully discloses the data sources (Sentinel-1/2 SAR, Hansen GFC) and outputs (cryptographic evidence hash, EU TRACES-NT DDS reference format), which is real behavioral context. However, it says nothing about permissions/auth, latency, cost, determinism, or whether the audit mutates any state, which for an unannotated tool is a notable 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?

Two dense sentences that front-load the purpose and then the methodology/output. Everything earns its place, though the second sentence is packed with acronyms (SAR, GFC, TRACES-NT, DDS) that could be trimmed or expanded for readability.

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 annotations, no output schema, and five parameters, the description does cover what it does and roughly what it produces. It stops short of the guidance an agent needs to route between it and the numerous verify_* siblings, leaving contextual completeness only adequate.

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 five parameters (latitude, longitude, country_code, area_hectares, concession_id). The description adds no syntactic or semantic detail about the parameters beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (audits), a precise resource (mining concession plot coordinates), and the regulatory standard it checks against (EUDR EU 2023/1115, 2020-12-31 cutoff, indigenous territory boundaries). This is clearly distinguishable from the verify_*_origin siblings, which target mineral origin provenance rather than plot-level deforestation audits.

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 EUDR/compliance framing implies when the tool is relevant, but there is no explicit when-to-use statement, no conditions that select it over verify_mineral_lot_compliance or get_compliance_status, and no exclusions. Usage is left to inference from the regulatory context.

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