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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, but the description adds nothing beyond that: no default limit, no sort direction, no explanation of what 'level' or 'period' values are accepted. For an open-world ranking tool with zero enum constraints, the description leaves the agent guessing about valid input.

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?

It is short and front-loaded, but so telegraphic that the brevity comes at the cost of meaning. The filter list is essentially a duplicate of the schema keys with no added value.

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?

Four undocumented parameters, no output schema, and only bare annotations mean the agent has almost nothing to build a valid call from. The description should at minimum define accepted metric/period/level values and the default result size.

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% and there are no enums, so the description carries the full burden for all four parameters. It only names them (metric, period, level, limit) without saying what metric keys exist, what period format is expected, or what 'level' distinguishes.

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?

It states the resource (a ranking of courts) but no verb or scope, and 'Ranking sądów' is close to restating the tool name. It doesn't distinguish the tool from siblings like get_sad, get_sedzia or search_administracja, so an agent can't tell what a 'ranking' yields versus a single-entity lookup.

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 instead of get_sad or the search_* siblings. The trailing list of filter names is a restatement of the schema, not a usage condition.

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