regdata_bdo_waste_registry

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

Mentions 'No API exists' implying scraping, which sets expectations. No annotations provided, so description carries behavioral burden. Lacks details on rate limits, error handling, or data freshness.

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?

Front-loaded with purpose, then details. Mostly efficient, but includes redundant Polish phrases ('Gospodarka odpadami') and some promotional language that could be trimmed.

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?

Lacks output schema and doesn't describe return values or result structure. Could mention what entities are returned or pagination behavior. Incomplete given scraper complexity.

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?

Adds meaning beyond schema by specifying freeform input examples (name, tax ID, registration number) and noting it matches Apify actor input schema. Schema itself only documents maxItems, description compensates with usage hints.

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 it's a Poland BDO Waste Registry scraper, targeting waste management entities, permits, waste codes, provinces. It distinguishes from many European registry siblings by naming the specific Polish waste database.

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?

Describes passing a flat search object (e.g., name, tax ID, registration number) and suggests calling regdata_describe first if unsure. Provides clear context but no explicit when-not-to-use or alternatives.

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