regdata_belgium_kbo_company

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

No annotations provided, but description clearly states it is a scraper accessing official public search, with no API key required. This sufficiently conveys the read-only, external data fetching nature.

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?

Description is informative and well-structured, with key information front-loaded. A minor redundancy exists between the title and initial phrase, but overall efficient.

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?

Covers input format, data returned, and fallback guidance. Lacks output structure description but is acceptable for a scraper without output schema. For the complexity, it is sufficiently 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 defines only maxItems, but description adds critical context: input must be a flat object with fields like name or tax ID, and recommends using regdata_describe for exact fields. This compensates for the freeform schema.

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?

Description clearly states the tool scrapes Belgium's KBO/BCE registry for company data including directors and VAT, with lookup by enterprise/VAT number or name. This specificity distinguishes it from other registry scrapers.

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 clear context for use: scrapes Belgian public registry, no API key needed, and advises using regdata_describe to verify input fields. Does not explicitly state when not to use but gives indirect guidance via sibling context.

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