Polish Academic MCP

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

No annotations are provided, so the description carries the full burden. It discloses the tool's behavior as a fetch operation that returns metadata and an embedded books list, but lacks details on error handling, rate limits, authentication needs, or response format. This is adequate for a read-only tool but misses some behavioral context.

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 zero waste: the first states the purpose and output, the second provides usage guidance. It is front-loaded with essential information and efficiently structured.

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?

Given a simple tool with one parameter (100% schema coverage), no output schema, and no annotations, the description is reasonably complete. It covers purpose, usage, and parameter context, but could improve by including more behavioral details like error cases or response structure, which are not critical for this low-complexity tool.

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%, with the schema fully documenting the 'slug' parameter. The description adds minimal value by implying the slug comes from 'API or site URL' and referencing 'wolnelektury_list_taxonomy' for obtaining slugs, but doesn't provide additional syntax or format details beyond the schema's description.

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 clearly states the specific action ('Fetch') and resource ('one thematic collection by slug') with explicit scope ('metadata + embedded books list'). It distinguishes from sibling tools by mentioning 'wolnelektury_list_taxonomy' for listing collections, avoiding redundancy with other WolneLektury tools like 'wolnelektury_get_book' or 'wolnelektury_filter_books'.

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 explicitly provides when to use this tool ('Fetch one thematic collection by slug') and when to use an alternative ('Use wolnelektury_list_taxonomy with kind=collections to list collection slugs and titles'), offering clear guidance on tool selection and prerequisites.

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