lookup_by_cadastral

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

No annotations provided, so the description carries full burden. It discloses that only open data is returned (no owner PII), which is a behavioral trait. However, it does not mention rate limits, authorization requirements, or what happens with invalid numbers, leaving gaps.

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?

Three sentences, front-loaded with purpose, no redundant or extraneous content. Every sentence adds value: what it does, input format, output fields, data limitations.

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?

For a simple data lookup with 2 parameters and an output schema (not shown), the description covers the main purpose, input format, output types, and data scope. Missing details on the include_geometry parameter and potential error states, but overall adequate for basic understanding.

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%, so the description must compensate. It provides format guidance for the required cadastral_number parameter (example and pattern) but does not explain the optional boolean parameter include_geometry. The listed return fields are helpful but not directly linked to the parameters.

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 the tool retrieves public characteristics by cadastral number, including a format example. However, it does not explicitly differentiate from sibling tools like get_cadastral_value, lookup_by_address, or lookup_by_coords which use different input methods.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage when you have a cadastral number but does not mention that other input methods are covered by sibling tools, nor does it provide exclusions or prerequisites.

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