getapi_property_energy-label

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing beyond the HTTP GET endpoint. It does not state authentication needs, rate limits, error behavior for invalid addresses, or what the response contains; only the GET method implies read-only.

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 front-loaded phrase with no filler, which is efficient. However, its extreme brevity leaves gaps that a slightly expanded definition could have filled without becoming verbose.

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?

Given four parameters at 0% description coverage, no annotations, and no output schema, the one-line description is far too thin. It omits required parameter semantics, return values, and behavioral context that an agent would need to invoke the tool correctly.

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% across four parameters, and the description only says 'Dutch address' without mapping any meaning to zipcode, house_number, house_letter, or house_number_addition. It does not compensate for the undocumented schema fields at all.

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 gives a specific verb ('lookup') and resource ('energy label') scoped to a Dutch address. It is immediately distinguishable from sibling tools like getapi_property_pandgegevens or getapi_lookup_postcode by its unique energy-label subject.

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?

The description implies usage through 'Dutch address' but gives no explicit when-to-use guidance, no prerequisites, and no alternative tools for related property lookups. An agent must infer all routing decisions from the purpose alone.

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