Check Process Id In Codelist

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose an important external dependency (EINVOICING_PEPPOL_CODELIST_DIR), which is valuable. However, it does not mention failure behavior or what happens when the environment variable is missing, and it leaves return semantics to the output schema.

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 two concise sentences with no filler: the first states the tool's purpose and the second adds the key prerequisite. The essential information is front-loaded.

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 simple two-string codelist check with an output schema, this is minimally adequate: it gives purpose and dependency. But it lacks a pointer to list_process_ids for retrieving valid identifiers and provides no detail about valid scheme/value forms, leaving the agent to infer important context.

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 0%, so the description needed to explain the parameters. It only restates that the input is a '(scheme, value) pair' and labels it a process identifier, without explaining valid scheme formats, value formats, or how to discover valid process IDs. This is insufficient compensation for the missing schema descriptions.

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 uses a specific verb ('Check whether') and a specific resource ('Peppol process identifier'), and clarifies that the input is a (scheme, value) pair. This makes it easy to distinguish from sibling check_* tools that target participant IDs, document types, and other codelists.

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 provides a useful prerequisite (EINVOICING_PEPPOL_CODELIST_DIR) and points to list_participant_id_schemes, but it does not explicitly explain when to choose this tool over list_process_ids or the other check_* tools. The intended usage is implied by 'Check whether', not stated as a decision rule.

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