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 of behavioral disclosure. It describes what the tool returns (hypermedia links to dump sub-services) and provides a documentation URL, but doesn't mention rate limits, authentication requirements, or what format the links are in. The description adds some context but lacks comprehensive behavioral details.

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 efficiently structured in two sentences: the first explains the tool's function, the second provides usage guidance and documentation reference. Every element serves a purpose with no wasted words, and key information is front-loaded.

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 zero-parameter tool with no annotations and no output schema, the description provides good context: it explains what the tool returns (hypermedia links to specific sub-services), when to use it versus alternatives, and includes documentation reference. The main gap is lack of output format details, but overall it's reasonably complete for this tool type.

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 tool has 0 parameters with 100% schema description coverage. The description appropriately doesn't discuss parameters since none exist, and it focuses on explaining what the tool does rather than parameter details. This meets the baseline expectation for a zero-parameter tool.

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 tool's purpose: it's a bulk dump API entry that lists hypermedia links to specific dump sub-services (commonCourts, judgments, scChambers, enrichments, deletedJudgments). It uses specific verbs ('lists', 'dump') and distinguishes itself from sibling tools by mentioning saos_search_judgments as an alternative for different use cases.

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 provides explicit guidance on when to use this tool versus alternatives: it states 'For searching judgments without mirroring the full database prefer saos_search_judgments.' This clearly defines the boundary between this bulk dump entry point and the search-focused sibling tool.

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