Eén rijschool

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

Without annotations, the description carries the burden of disclosing side effects or read-only behavior. It implies a read operation by saying 'gegevens' but does not explicitly state that no modifications occur, nor does it mention error behavior or data availability guarantees.

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, reasonably concise sentence that lists the data fields. It front-loads the main purpose ('Alle gegevens van één rijschool') and avoids unnecessary fluff, though the long enumeration makes it slightly dense.

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 does not clarify parameter combinations or whether at least one parameter is required, especially since all parameters are optional in the schema. There is no output schema and no indication of return format, leaving ambiguity about how to invoke the tool correctly.

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?

All three parameters have descriptions in the schema, and the schema coverage is 100%. The parameter descriptions add useful context, such as using 'naam' when the ID is unknown and using 'stad' to disambiguate common names, going beyond simple field labels.

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 that the tool returns 'alle gegevens' (all data) of a single driving school and enumerates the specific data fields. It distinguishes from siblings by emphasizing 'één rijschool' (one driving school), though it does not explicitly name alternative tools.

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 provides no guidance on when to use this tool versus the sibling tools such as 'zoek_rijscholen' or 'rijschool_in_de_buurt'. It does not mention any selection criteria, prerequisites, or typical use cases.

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