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

No annotations are provided, so the description carries the full burden. It discloses the return contents (11 questions, each with explanation and example) and the critical usage constraint that answers must not be inferred. It does not discuss permissions or side effects, but 'Geeft ... terug' makes the read-only getter behavior evident.

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 purpose is front-loaded in the first clause, followed by the essential usage constraints. The capitalized emphasis is longer than ideal but every sentence carries operational weight (individually, literally, no self-fill, no steering).

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?

With no output schema, the description must carry the return information, and it does: item count and per-item structure (neutral explanation + example). For a simple zero-param getter with no annotations, this is essentially complete; only sibling routing is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly implies a parameterless fetch.

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?

States a specific verb and resource: it returns the 11 official GMCA Certainty Matrix Validate questions, each with a neutral explanation and example. The scope and content are unambiguous, though it never explicitly distinguishes itself from the sibling explain_validate_question or submit_validate_answers.

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?

Gives strong behavioral directives: ask each question individually and literally, collect Ja/Deels/Nee per question, never self-fill from a project description, and only share the explanation when the user doubts without steering the answer. It lacks explicit routing versus the siblings (e.g., 'call before submit_validate_answers'), which keeps it at 4.

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