eudr_check_deforestation

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

With no annotations, the description carries the full burden of behavioral disclosure but only describes the method, not whether the operation is read-only, side effects, or response behavior. An agent cannot determine if this check call is safe and what it returns.

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, front-loading the core action and deadline. It is efficiently written and every word contributes meaning.

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 meanings and the description gives the core function, but with no output schema and no annotation coverage, return values and behavioral details are missing. This makes the definition adequate but with clear gaps for an agent deciding how to invoke and interpret the call.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description adds some regulatory context for cutoff_date, but the schema already documents the default value, so the added value beyond the schema is minimal.

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 ('performs satellite radar triangulation and canopy loss detection') and the target regulatory deadline ('EUDR cut-off date of 31 December 2020'), so an agent can infer what the tool does. It doesn't explicitly contrast with siblings like eudr_verify_plot, so differentiation relies mostly on the name and method.

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 purpose implies when to use the tool, but there is no explicit guidance on context, prerequisites, or alternatives. It doesn't mention that eudr_verify_plot might be a broader verification option or when to prefer this specific deforestation check.

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