propertiesget_area_stats_deprecated

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, 'Get area stats' offers no information about behavioral traits such as whether this is a read-only operation, potential side effects, authentication requirements, rate limits, or response format. The description fails to compensate for the lack of annotations, leaving the agent with minimal insight into how the tool behaves.

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 'Get area stats' is overly concise to the point of under-specification. While it is front-loaded and wastes no words, it lacks essential details that would make it helpful. Conciseness should not come at the cost of clarity; here, the brevity results in insufficient information, failing to earn its place as a useful description.

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 the tool's complexity (deprecated status, single parameter), lack of annotations, and absence of an output schema, the description is incomplete. It does not explain what 'area stats' entails, how results are returned, or why it is deprecated compared to siblings like 'house_pricesget_area_stats_deprecated'. For a tool with no structured support, the description fails to provide the necessary context for effective use.

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 has 100% description coverage, with the single parameter 'listing_id' fully documented in the schema. The description does not add any meaning beyond what the schema provides, as it mentions no parameters. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter semantics without needing additional explanation in the description.

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 'Get area stats' is a tautology that merely restates the tool name 'get_area_stats_deprecated' with minor wording changes. It lacks specificity about what 'area stats' refers to (e.g., property statistics, demographic data, market metrics) or what resource is being accessed. While it includes a verb ('Get'), it does not distinguish this tool from its many siblings, such as 'house_pricesget_area_stats_deprecated' or 'propertiesv2detail', leaving the purpose vague.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, nor does it refer to sibling tools like 'house_pricesget_area_stats_deprecated' or 'propertiesv2detail' that might serve similar purposes. This absence of usage instructions makes it challenging for an AI agent to determine the appropriate scenario for invocation.

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