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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses that the tool merges multiple data sources, includes live statutory details with dates and committees, and conditionally includes parcel-level plans only when gush+helka is provided. This gives the agent meaningful expectations about scope and conditional behavior.

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 dense but front-loaded with the core purpose ('Unified full picture') and then enumerates the merged components and accepted identifiers. The long single-sentence structure and unexplained references to Card A/B/E make it slightly harder to parse quickly, but every part contributes useful information.

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?

The description covers both inputs and outputs at a practical level: what data sections will be returned and the identifier alternatives. It does not explicitly state that at least one identifier is required even though the schema marks all six parameters as optional, and it leaves some ambiguity about whether city alone can identify a single compound. Still, it is largely complete for an aggregation tool of this complexity.

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 input schema already documents all six parameters clearly. The description adds the notion that identification can happen via any of several identifiers and that gush+helka triggers parcel-level plans, but these are largely implied by the parameter names and schema descriptions. Baseline 3 is appropriate.

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 identifies the tool as an aggregator for one Israeli urban-renewal compound, specifying the exact data sources merged: registry status, iplan statutory detail, VATMAL compounds, and parcel-level plans. This distinguishes it from the narrower sibling tools such as urban_renewal_registry, vatmal_compounds, planning_by_parcel, and planning_status_by_plan.

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 explicitly frames the tool as providing the 'unified full picture' for a single compound, which makes the primary use case clear. It does not name alternatives or state when not to use it, but the aggregation language implies this is the comprehensive option rather than a specific single-source lookup.

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