Peppol Lookup Participant

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

With no annotations provided, the description carries the transparency burden. It explicitly discloses a concrete multi-step network behavior: DNS-over-HTTPS U-NAPTR lookup followed by an SMP service-group request. The word 'check' also implies a read-only operation. It does not cover timeouts, failures, or rate limits, but the core behavioral profile is clear.

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 tight sentences with no wasted words. The core purpose is front-loaded, and the second sentence adds meaningful process detail without fluff.

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?

Given that the parameters are fully documented and an output schema exists, the description is largely sufficient for correct invocation. It explains the underlying DNS/SMP behavior, but it does not address selection among overlapping sibling tools or potential failure/prerequisite conditions, so it is not fully 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 100%, and the schema already documents both identifier and environment in detail. The description adds no parameter-specific meaning, so the baseline score of 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?

The description opens with a specific verb and resource: 'Check whether a business is registered on the Peppol network.' It further defines the result as both registration status and supported document type identifiers, which clearly separates it from sibling tools like resolve_peppol_dns or peppol_get_service_endpoint.

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 intended use is implied by the purpose statement, but there is no explicit when-to-use or when-not-to-use guidance. Overlapping sibling tools such as resolve_peppol_dns, peppol_get_service_endpoint, and peppol_directory_search are not mentioned, so an agent gets no direct routing help.

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