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

No annotations are supplied, so the description carries the full burden, yet it says nothing about the operation being a safe read, whether authentication is required, how results are ordered, or what happens when filters match nothing. The only behavioral hint is "(частини назв)" for region, which implies substring matching. For a tool with zero annotation coverage, this leaves significant gaps.

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 short line with the key fields front-loaded and no filler. It is terse to the point of being cryptic (the parenthetical is unexplained), but nothing is wasted or buried.

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?

The tool is simple (three optional filters, no output schema, no nesting), so a short description can suffice, but this one omits return shape, pagination implications of limit, and any hint of the matching semantics for name. Given no annotations and no output schema, the description should do noticeably more.

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 0%, so the description must compensate, and it partly does: it lists all three parameters and clarifies that region matches on parts of names. It does not explain the matching rule for name, the default or maximum value of limit, or whether empty strings mean "no filter". Partial compensation only.

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 names the resource as a court directory ("Довідник судів") and enumerates the filter fields, so an agent can infer it returns a list of courts. However, it uses a noun phrase with no verb, and it never distinguishes itself from the sibling court_category_stats, which also addresses courts. The purpose is understandable but imprecise.

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 statement of when to use this tool versus siblings such as court_category_stats or the search_* tools, and no prerequisites or exclusions are given. The agent must infer from the name alone that this is a reference/lookup endpoint used to resolve court identifiers.

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