tweede_kamer_documents

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

Annotations already indicate read-only and open-world behavior. The description adds that it searches documents and filters, but does not disclose pagination, ordering, or other traits beyond what annotations provide.

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 two concise sentences, front-loaded with the main action, and every sentence adds value without fluff.

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 basic search action but lacks details on pagination, output format, and differentiation from similarly named siblings. Given 10 parameters and no output schema, it is not fully complete for complex usage.

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 meaning to the 'query' parameter (policy keywords) and mentions filters for type and date range, but does not explain the other 7 parameters (top, limit, offset, outputFormat, verbose, dryRun, etc.), especially with schema coverage at only 10%.

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 it searches Dutch Parliament documents with policy keywords and optional filters. However, it does not differentiate from the sibling 'tweede_kamer_search', which appears to have the same name.

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?

It suggests using policy topic keywords and optionally filtering, but gives no guidance on when to use this tool versus alternatives like 'tweede_kamer_search' or 'tweede_kamer_document_get'.

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