getapi_property_pandgegevens

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no authentication requirement, no indication whether every pandgegevens record is returned or whether some addresses yield empty results, no error semantics, no rate-limit note. For an external lookup API with zero structured coverage this is a serious gap.

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?

It is a single short, front-loaded line with no wasted words and it usefully carries the endpoint path. The brevity, however, reflects under-specification rather than disciplined concision.

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 four-parameter external property lookup with no annotations and no output schema needs the description to explain inputs, expected results, and error/empty-result behavior. None of that is present, so an agent cannot call this tool confidently.

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?

Four parameters with 0% schema description coverage and no annotations, yet the description mentions none of them. The untyped house_letter and house_number_addition fields (no type, no description) are completely unexplained, and the required postcode/house_number pairing is only discoverable from the schema.

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 essentially restates the tool name plus the HTTP path: "Property data lookup (pandgegevens) [GET /v1/property/pandgegevens]". It adds almost nothing about scope, what data is returned, or how it differs from the sibling getapi_property_pandgegevens-lite, which is never mentioned.

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 when-to-use guidance, no prerequisites, and no routing to the -lite variant or to getapi_kadaster_bag_address, which covers overlapping Dutch address/property data. The agent is left to infer usage entirely from the tool name.

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