regdata_polish_premises

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

No annotations are provided, so the description must disclose behavioral traits. It notes that the input is freeform and matches Apify's schema, and suggests using regdata_describe for field discovery. However, it does not mention whether the tool is read-only, any rate limits, or authentication requirements. For a data lookup tool, the description is adequate but not fully transparent.

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 sentences, front-loaded with the core purpose and key details. Every sentence adds value, with no wasted words.

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 no output schema and no annotations, the description covers the tool's purpose, input format, return content, and a usage hint (regdata_describe). It does not explain prerequisites like API keys, but such details are likely shared across the regdata tool family. The description is complete enough for an AI agent to understand how to invoke the tool.

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 coverage is 100% (the only parameter 'maxItems' is described). The description adds context that the input is freeform and the tool matches Apify's schema, and advises using regdata_describe for field details. This goes beyond simply repeating 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?

The description clearly states the tool's purpose: 'Build prospect lists at the physical-site level from the Polish REGON registry.' It specifies the content (industry, address, company age, ownership) and filtering (by region TERYT). This distinguishes it from sibling tools like regdata_polish_regon which likely operate at the company level.

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 clear guidance: 'pass the registry's search input as a flat object' and advises to call regdata_describe first if unsure of exact fields. It does not explicitly state when not to use this tool or compare to siblings, but the context is sufficient for basic usage.

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