eudr_score_kfs_checklist

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Evaluates' implies a read/scoring operation, but the description does not state whether it persists data, requires authentication, is idempotent, or what side effects exist.

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?

A single front-loaded sentence with no wasted text. The verb, resource, authority, domain count, and scoring scale are all included efficiently.

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?

No output schema exists, so the description should ideally say more about the return value than just the 100-point scale. It gives a useful hint that a score is returned, but does not describe output structure, domain-level breakdowns, or how the result should be interpreted.

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 both parameters are already documented in the input schema. The description references the payload being evaluated but adds no syntax, format, or validation meaning beyond what the schema provides, so baseline 3 is appropriate.

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 (Evaluates), resource (EUDR supply chain payload), and scoring standard (official Korea Forest Service 4-domain compliance checklist, 100-point scale). This distinguishes it from sibling evaluation tools such as eudr_evaluate_compact, eudr_evaluate_customs_taric, and eudr_check_deforestation.

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?

No explicit when-to-use guidance, prerequisites, or alternatives are provided. An agent must infer that this is the KFS checklist scoring tool rather than one of the many sibling evaluation or verification tools.

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