Wat een rijles kost

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

The description discloses the data source (driving school websites) and notes prices are indicative. It does not mention any side effects or explicitly state that the tool is read-only, but given the absence of annotations, the description is reasonably transparent about the expected behavior of returning price statistics.

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 a single, concise sentence that conveys all essential information without redundancy or unnecessary detail. It is well-structured and easy to parse.

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 description covers the core output (cheapest, median, most expensive) and the geographic scope options. It does not specify the exact return format or the behavior when both parameters are used, but for a simple price-statistics tool, this is largely sufficient. Minor gaps prevent a perfect score.

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 description adds that parameters limit scope to a single city or province, and that omitting both yields national results. However, it does not elaborate on the interaction when both 'stad' and 'provincie' are provided, leaving ambiguity about whether they combine or one takes precedence.

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: providing the price distribution (cheapest, median, most expensive) for driving lessons, with scope options (national, city, or province). It explicitly distinguishes this from sibling tools that locate driving schools or list cities/provinces.

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 implies usage for price statistics (e.g., when you need cost comparisons) but does not explicitly state when to use this tool over alternatives like 'zoek_rijscholen' or 'rijschool'. It lacks direct guidance on choosing between national vs. local scopes or clarifying the effect of combining both parameters.

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