resolve_property

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 a dependency on Datafordeleren for BFE, which is useful, but it doesn't mention that this is a read-only operation, potential rate limits, error behavior, or that it may require external credentials. The disclosure is minimal.

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, efficient sentence that front-loads the core purpose and includes the key dependency. It is concise without wasted words, though it lacks any structured breakdown of inputs/outputs.

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 there is no output schema, the description lists the types of data returned (DAR IDs, coordinates, etc.), which is helpful. However, it omits behavior on failure, how query and addressId interact, and whether both can be provided. For a resolve tool with 2 optional parameters, it is adequate but not thorough.

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 100% and both parameters are described ('Free-text address if addressId is unknown' and 'DAR address UUID'). The description adds no additional parameter meaning, such as how the two parameters interact or whether they are mutually exclusive. Baseline 3 is appropriate since the schema carries the detail.

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 states a clear verb ('resolve') and resource ('Danish address') with specific outputs (DAR IDs, coordinates, cadastral IDs, BFE). It is distinct from siblings like search_address which likely just finds an address, but it doesn't explicitly name the sibling it differentiates from.

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?

No guidance is given on when to use this tool versus search_address, property_report, or get_parcel. The only mention is a prerequisite ('Requires Datafordeleren for BFE'), not a usage condition or exclusion. An agent would have to infer intent from the outputs listed.

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