UK Property Data

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

With no annotations provided, the description carries full burden. It discloses the tool analyzes Land Registry transactions and groups them by building, which is useful context. However, it doesn't mention rate limits, data freshness, authentication requirements, or what the output format looks like. The behavioral disclosure is adequate but incomplete for a tool with no annotation coverage.

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 perfectly concise: two sentences that immediately convey the tool's purpose and value proposition. Every word earns its place, with no redundant information. The first sentence states the core function, and the second explains the analytical 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 tool with no annotations and no output schema, the description provides adequate purpose and context but leaves significant gaps. It doesn't describe what the output looks like (format, structure, fields), doesn't mention data sources or limitations, and doesn't provide error handling guidance. Given the complexity of property transaction analysis, more completeness would be beneficial.

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%, so the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. However, with only 3 parameters and excellent schema coverage, the baseline is appropriately high. The description's focus on 'blocks being sold off' and 'bulk-buy opportunities' provides helpful context for why someone would use these 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's purpose: 'Find buildings with multiple flat sales' and 'Groups Land Registry transactions by building to identify blocks being sold off, investor exits, and bulk-buy opportunities.' It specifies the verb (find/identify), resource (buildings with multiple flat sales), and distinguishes from siblings by focusing on block-level analysis rather than individual property searches.

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 context ('block buying opportunities', 'investor exits', 'bulk-buy opportunities') but doesn't explicitly state when to use this tool versus alternatives like property_comps or ppd_transactions. It provides general intent but lacks specific comparative guidance with sibling tools.

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