kio_search

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

Annotations already indicate readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds that pzp_article is a post-process filter, which provides context beyond annotations. However, it does not disclose other behavioral aspects like API dependency or pagination behavior beyond schema.

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?

Two concise sentences: first defines purpose, second adds key context about optional parameters and pzp_article filter. No unnecessary words, front-loaded with 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?

Given 10 parameters, multiple siblings, and presence of an output schema, the description is minimal. It lacks context on when to use siblings, result format, or additional constraints. Sufficient for basic use but incomplete for complex decision-making.

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 has 100% coverage with parameter descriptions. Description adds that pzp_article is post-process (no server-side), which clarifies its behavior. Baseline is 3 due to full schema coverage; the added semantic value raises the score to 4.

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?

Description states 'Wyszukuje orzeczenia KIO w bazie orzeczenia.uzp.gov.pl', clearly specifying the action (search) and resource (KIO decisions). It distinguishes from siblings like kio_by_pzp_article, kio_recent, etc., by being the general search tool.

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?

No guidance on when to use this tool vs alternatives. Only mentions that all parameters are optional and that pzp_article is a post-process filter. Does not explain when to choose this over specific siblings like kio_by_pzp_article.

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