ezd_koszulka_list_documents

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

The annotations declare readOnlyHint=true, and the description merely restates a read operation ('Pobierz liste'). It adds no extra behavioral context such as filtering behavior, pagination, ordering, return shape, or side effects. No contradiction exists, but the description does not go beyond what the annotation already implies.

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 a single concise sentence with no filler or repetition. It is appropriately front-loaded, though it is so terse that it leaves out useful operational context. Still, for pure conciseness and structure, it is effective.

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 no usage guidance, a one-line description is not enough for an agent to understand what the tool returns, how to combine the seven optional parameters, or how this relates to sibling folder/document tools. The rich parameter schema helps, but the overall contextual picture is incomplete.

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?

All seven parameters have individual schema descriptions, so schema coverage is 100%. The description itself does not explain parameter usage, but it also does not need to compensate because the schema field descriptions are complete.

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 uses a clear verb ('Pobierz') and a specific resource ('liste dokumentow w koszulce'), so an agent can tell it lists documents contained in a koszulka/folder. It does not explicitly contrast itself with siblings like ezd_koszulka_list, but the wording is specific enough to avoid major confusion.

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 alternatives such as ezd_koszulka_get, ezd_koszulka_list, or ezd_dokument_get_metadata. No conditions, exclusions, or preferred selection criteria are provided.

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