Realty In Ca1 MCP Server

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

With no annotations provided, the description carries full burden but fails to disclose the deprecation status, does not explain what specific statistics are returned (demographic? market? price?), and omits any mention of rate limits or data freshness. The 'CultureId' parameter behavior is also unexplained.

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 single-sentence structure is appropriately brief, but the sentence fails to earn its full place by omitting critical deprecation context that should have been front-loaded. The 'surround area' phrasing is slightly awkward.

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 appears deprecated (per name), has closely related siblings, and lacks an output schema, the description is incomplete. It fails to warn users away from using a deprecated endpoint or explain what data structure to expect in return.

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%, establishing a baseline of 3. The description mentions 'GEO location' which loosely maps to the Longitude/Latitude parameters, but adds no syntax details, format constraints, or explanation of the CultureId default value (1 for English).

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 states the basic action ('Get statistic information') and method ('by GEO location'), but fails to acknowledge the deprecated status evident in the tool name or differentiate from similar siblings like 'propertiesget_demographics' and 'propertiesget_scores'. The typo 'surround' instead of 'surrounding' also slightly impairs clarity.

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 guidance provided on when to use this tool versus alternatives, nor any mention that it is deprecated despite the '_deprecated' suffix in the name. Critical omission regarding whether users should avoid this tool in favor of 'propertiesget_demographics' or 'propertiesget_scores'.

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