Get KKTC Property Legal Information

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

Annotations already declare readOnlyHint and openWorldHint. The description adds important context: it is a general routing tool, not a definitive legal resource, and recommends lawyer consultation. This clarifies its non-definitive nature beyond what annotations provide.

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?

Two concise sentences, front-loaded with main purpose. No filler or redundant information. Every sentence adds value.

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 read-only tool with one parameter and an output schema, the description covers purpose, topics, and a crucial disclaimer. It is nearly complete; only missing fine-grained usage guidance relative to siblings.

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?

The input schema only labels topic as 'Legal topic to retrieve' with no enum descriptions. The description lists the actual topics (kocan_types, foreign_purchase, etc.) with brief context (e.g., 'title deed types (koçan)'), adding significant meaning beyond 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 clearly states it provides general legal/procedural routing for Northern Cyprus property topics, listing key areas. It distinguishes from siblings like foreign_buyer_roadmap by emphasizing its routing nature, though not explicitly differentiating from all.

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 use for informational routing and advises consulting a lawyer for specific cases, but does not explicitly state when not to use it or how it compares to related tools like foreign_buyer_roadmap or assess_title_risk.

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