regdata_germany_handelsregister

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

Describes that it is a scraper with no official API, returns structured JSON for KYC, and lists extracted fields. No annotations exist, so the description carries the full burden; it adds moderate transparency but lacks details on error handling or limitations.

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 efficient, with every sentence providing essential information: purpose, output, and usage guidance. No wasteful text.

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?

Explains input format, output content, and a prerequisite step. Without an output schema, it adequately describes the return values. Could be improved by mentioning limitations or error responses, but overall sufficient.

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?

The schema only defines maxItems, but the description explains that search fields (name, tax ID, etc.) should be passed as additional properties, and advises calling regdata_describe for exact fields. This adds significant meaning beyond the 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?

Clearly states it searches the German Commercial Register by company name or register number, and extracts specific data. Distinguishes from siblings by being Germany-specific.

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 explicit instruction to pass search input as a flat object and to call regdata_describe first if unsure. Does not explicitly exclude other cases, but the context of sibling tools implies appropriate use.

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