Eén begrip

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

No annotations are provided, so the description carries the burden. It describes an informational lookup returning an explanation, which implies no side effects. However, it does not explicitly state read-only behavior or lack of mutations, so it falls short of full transparency.

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 clear sentence, comprehensive without being verbose. It is well-structured and front-loads the main 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?

The description enumerates what the explanation covers (definition, rules, mistakes, confusions, legal articles), giving a thorough picture of the output. For this simple tool, no additional context is necessary.

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 schema fully describes the 'term' parameter with an example, so coverage is high. The tool description adds no extra parameter details, remaining at the baseline.

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 this tool provides the full explanation of a single concept, distinguishing it from sibling tools like 'begrippen' (plural list) and 'zoek' (search). The verb is implied but the intent is unambiguous.

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?

While the singular focus is clear, the description does not explicitly mention when to use this tool versus alternatives like the plural 'begrippen' or search. It relies on the user inferring the distinction from the title and description.

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