regdata_bdo_waste_registry

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

With no annotations, the description carries the full burden. It clearly identifies the tool as a scraper that reads from a public register, and specifies limitations (no API, no login access). It could explicitly state it is read-only, but the context implies safe, non-destructive use.

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 front-loaded with the key action and resource. It efficiently packs purpose, return data, limitations, and a pointer to additional fields. While slightly verbose, it avoids redundancy and each sentence serves a purpose.

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?

For a tool with 4 parameters and no output schema, the description covers purpose, data returned, limitations, and parameter behavior (via schema). It explains pagination in maxResults and provides enough context for an agent to decide when to use it. Lacks explicit description of error cases or empty results.

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%, baseline 3. The description adds value by contextualizing the search query (674,000+ entities by name/NIP) and noting that advanced fields are accepted via regdata_describe. This goes beyond the schema's definitions.

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 precisely states the tool searches the Poland BDO Waste Registry by name or NIP, returning specific fields (BDO number, company name, NIP, address). It explicitly answers the question 'is this company in the BDO register?' distinguishing it from other Polish registry tools listed as siblings.

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 tells when to use (checking BDO registration for ESG/due diligence) and explicitly states what NOT to use it for (waste codes/permits are behind login). It also directs to regdata_describe for advanced fields. However, it does not contrast with specific sibling tools.

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