regdata_uokik_clauses

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

No annotations provided. Description mentions it is a 'scraper' and returns JSON, and that the input is a flat object with search fields. However, it lacks details on rate limits, authentication, error behavior, or whether it is strictly read-only. Adds some context but not comprehensive.

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 4 sentences, each providing useful information: purpose, statistics, search criteria, and usage instruction. Could be slightly more concise, but each sentence earns its place.

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?

No output schema exists. Description notes output is JSON but does not specify structure or fields. It mentions number of clauses but not pagination or error handling. The advice to use regdata_describe for input fields partially compensates, but output details are lacking.

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 input schema only defines maxItems; the description explains that the main input is a flat object with fields like name, tax ID, etc., and directs to regdata_describe for exact fields. This adds meaningful guidance beyond the schema, which is minimal.

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 the tool is a scraper for Poland UOKiK Abusive Clauses Registry, with specific verbs ('Search') and resources ('court-banned contract clauses'). Distinguishes from siblings by country and content type.

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 context for legal compliance/consumer protection and advises calling regdata_describe first if unsure of fields. Does not explicitly state when not to use this tool, but the sibling list and description make it clear it's for Polish clauses only.

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