ezd_api3_search_epuap_outflow

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

The annotation readOnlyHint=true already marks the tool as read-only, and the verb 'Wyszukaj' is consistent with a non-mutating lookup. The description adds no further behavioral detail such as auth requirements, result ordering, or rate limits, so it is adequate but not rich.

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 sentence with the verb and resource front-loaded, followed by the search criteria. There is no filler, no repetition, and each part contributes to understanding the tool.

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 search tool with 7 optional parameters and no output schema, the description states the searchable keys but does not clarify whether at least one criterion is expected, how multiple criteria combine, or what the result shape is. Parameter meanings are covered by the schema, but the tool-level invocation contract has gaps.

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 has 100% description coverage, including defaults and auto-generation for CID. The description only summarizes the grouping of criteria and does not add meaning beyond the schema, so the baseline of 3 applies.

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 opens with 'Wyszukaj' (search), names the resource (ePUAP outflows/outgoing shipments), and lists the search keys (document identifier, correlation, correspondence, koszulka). This also distinguishes it from siblings like ezd_api3_search_epuap_inflow and ezd_api3_search_paper_outflow.

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?

It gives clear context: use this when you need to find ePUAP outflows by document, correlation, correspondence, or case identifiers. It does not explicitly name alternatives or exclusion conditions, so it stops short of a 5.

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