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

No annotations exist, so the description carries the full disclosure burden. It hints that results are filtered to towns that have secondary schools and that counts are included, but says nothing about ordering, result limits, or how the count filter behaves — thin for a tool with zero annotation coverage.

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?

One short, front-loaded sentence with no filler. It is efficient, though it reads as a fragment rather than a complete statement of purpose.

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 simple one-parameter tool this is still under-specified: the only parameter is undocumented and there is no usage context. No output schema exists, so the description would need to signal what a result looks like, and it does not.

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 single parameter min_count has 0% schema description coverage and is never mentioned in the description. The phrase 'school counts' gestures at count-based selection but does not explain that min_count sets the minimum number of schools, so the parameter's meaning is left entirely to inference.

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 phrase names a resource and a scope ('Hungarian towns with secondary schools and school counts'), which distinguishes it from the school-oriented siblings, but it contains no verb and never says it lists or returns towns. An agent can guess the domain but not the action or the output shape from this alone.

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 when-to-use guidance, no exclusions, and no pointer to alternatives such as search_schools or compare_schools. The agent gets no help deciding between this and its siblings.

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