getapi_ndw_truckparking

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it only embeds "GET" in the endpoint path, which weakly implies a read-only retrieval. It says nothing about pagination, filtering behavior, authentication, or the shape of results for a 5-parameter list endpoint.

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 text is short, but this is under-specification rather than conciseness — a single fragment that spends its few words restating the name and endpoint instead of conveying anything an agent needs.

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?

A five-parameter tool with no annotations, no output schema, and 0% schema coverage receives essentially no supporting context. Nothing in the definition tells an agent how to invoke it correctly or what to expect back.

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?

Schema description coverage is 0% and the description adds no parameter meaning whatsoever. Five parameters (page, road, status, per_page, beschikbaar) are left completely undocumented, including the ambiguous Dutch field "beschikbaar" and the pagination pair.

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?

"Truckparking lijst" is essentially a Dutch restatement of the tool name plus the raw endpoint path, with no verb or scope added. It does signal that the tool returns a list of truck parking locations, but that much is already inferable from the name, so it reads as a tautology rather than a purpose statement.

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?

There is no indication of when to call this tool, what it is useful for, or how it relates to siblings such as getapi_ndw_emissiezones or getapi_ndw_laadpunten. An agent must infer usage entirely from the name.

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