check_process_id_in_codelist

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

No annotations exist, so the description carries the burden. It discloses an environment-variable dependency and makes the check semantics clear. It does not describe failure behavior or side effects, though 'Check' implies a read-only operation.

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 short sentences with no filler. The core purpose is front-loaded and the prerequisite is placed in a separate necessary sentence.

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 tool is a simple boolean codelist check and an output schema exists, so return structure need not be described. However, missing usage guidance and parameter-level detail leave the description merely minimally viable rather than complete.

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%, and the description only tells the agent the pair is for a Peppol process identifier. It does not explain valid scheme/value formats, examples, or point to list_process_ids for possible values, so parameter semantics remain under-specified.

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 operation: check whether a (scheme, value) pair is a recognized Peppol process identifier. It separates itself from sibling codelist checks by naming process identifier distinctly.

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?

Provides a prerequisite (EINVOICING_PEPOL_CODELIST_DIR) but no explicit when-to-use guidance or comparison with sibling tools such as list_process_ids or check_document_type_id_in_codelist. The agent must infer usage from the tool name and first sentence.

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