ezd_api3_search_addressees

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

The readOnlyHint annotation already covers the safety profile, and 'Wyszukaj' is consistent with that. The description adds no extra behavioral details such as result format, pagination, limits, or required-at-least-one filter behavior, but for a read-only search the annotation lowers the burden.

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?

A single well-formed sentence that front-loads the verb and resource, then enumerates all search criteria. There is no filler or redundant restating of the parameter schema.

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 an 11-parameter search tool with no output schema, the description could usefully state whether criteria combine as AND/OR, whether at least one is required, and what a successful response contains. The current description is minimally sufficient because the schema covers parameter meaning and the read-only annotation covers safety, but it leaves these operational questions open.

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 description coverage is 100%, so the schema already documents every parameter. The description's grouping of criteria roughly maps to AdresatTyp, AdresatAdresElektronicznyDoreczen, the address fields, and ePUAP, but it adds no constraints or combination rules beyond what the schema provides.

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 ('Wyszukaj'), the resource ('adresatow w systemie EZD PUW'), and the available search dimensions (type, e-delivery address, address data, ePUAP). However, it does not distinguish this tool from the sibling ezd_api3_search_inflow_addressee, so it misses the top tier.

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 implies the tool is for locating addressees by the listed criteria, but it never states when to prefer this over ezd_api3_search_inflow_addressee or ezd_api3_get_addressee. No explicit when-to-use or alternatives are provided.

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