Landelijke cijfers

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

No annotations are provided, so the description carries full responsibility. It implicitly describes a read-only query but does not explicitly state non-modifying behavior, side effects, or safety. This is a minor gap for a tool that appears to be a simple data retrieval.

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 concise, two sentences, with no redundancy. It efficiently conveys the returned data points and the tool's role without unnecessary details.

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?

Given the lack of an output schema, the description adequately lists the expected data fields (percentage, number of schools, number of exams). It does not describe the response format or pagination, but for the tool's simplicity, this is sufficient for an agent to call and interpret results.

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 parameter 'categorie' is described as 'Rijbewijscategorie, standaard B (auto)', adding meaning by indicating the standard value and domain. However, it does not clarify optionality or enumerations, though the description adds some value beyond the property name.

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 provides national statistics (average pass rate, number of schools, total exams) and frames it as a benchmark, distinguishing it from more specific sibling tools. The purpose is immediately understandable.

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 includes a practical hint ('ijkpunt waar je een losse rijschool tegen afzet') implying use for comparison against a single driving school. It does not explicitly mention alternatives or exclusions, but the context strongly suggests when to use this tool.

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