Szukaj towaru po nazwie

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns a shortened list of matches (UN number, name, class) and that full data requires a subsequent lookup_un call. This goes beyond a generic 'search' statement and sets expectations about the output and workflow.

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 with no filler. The main purpose is front-loaded, and the guidance to use lookup_un for full data is placed efficiently. Every 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?

For a single-parameter search tool with no output schema, the description is complete: it identifies the target, the accepted query types, the abbreviated return fields, and the next step in the workflow. No critical information for invoking it correctly is missing.

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 already fully describes the only parameter, query, as 'Fragment nazwy lub numeru UN'. The description adds that the search is PL/EN and matches names or UN fragments, but it does not provide additional syntax, formatting, or example values beyond what the schema already says. Baseline 3 is appropriate since schema coverage is 100%.

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 states a specific verb ('Wyszukuje' — searches), a specific resource ('towary niebezpieczne' — dangerous goods), and search criteria (name PL/EN or UN number fragment). It also differentiates itself from the sibling lookup_un by noting it returns a shortened list rather than full data.

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 clearly indicates when to use lookup_un after finding the right position, giving a sequential workflow. It does not explicitly state when not to use this tool (e.g., when an exact UN number is already known, lookup_un might be more direct), but the context is clear enough for an agent.

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