ezd_koszulka_registries

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

Annotations already declare readOnlyHint=true, and the description merely repeats a read-only retrieval action. It adds no behavioral context such as what 'rejestry' include, whether the result is paginated, or whether ownership parameters affect the returned data. Since annotations cover the safety profile, this is acceptable but not additive.

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 one short, front-loaded sentence with no filler. It communicates the core action and target resource immediately, and every word carries meaning.

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?

With no output schema and only a terse description, an agent cannot tell what 'rejestry' actually are, what kind of record set will be returned, or how the input parameters shape the result. There is also no sibling differentiation, leaving the agent under-informed for a tool with four parameters and a nested object.

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 all four parameters and the nested Koszulka object. The description adds no extra meaning about how the Koszulka object or owner IDs are used to select registries, so it neither improves nor harms parameter clarity beyond the schema.

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 ('Pobierz'/'retrieve') and resource ('rejestry powiazane z koszulka'), which is clear enough to understand the basic operation. It is somewhat ambiguous what exactly 'rejestry' refers to, but it is distinguishable from sibling tools like ezd_koszulka_get or ezd_koszulka_list.

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?

There is no guidance on when to use this tool versus the many related koszulka or registry tools. It does not mention alternatives, prerequisites, or scenarios where another sibling would be more appropriate.

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