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 for behavioral disclosure but provides minimal information. It does not clarify what constitutes the 'surround area' (radius/buffer), what demographic fields are returned, whether the operation is read-only, or any potential costs/rate limits associated with geospatial queries.

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 brief (8 words) and front-loaded, but underspecified given the lack of annotations and output schema. The phrase 'surround area' appears to be a typo or awkward phrasing for 'surrounding area', slightly reducing clarity.

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 that this tool returns demographic data (complex dataset) with no output schema and no annotations, the description is insufficient. It fails to enumerate the demographic dimensions available (e.g., median income, age distribution, population density) or explain the spatial aggregation method used for the 'surround area'.

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 ('Latitude of specific location', 'Longitude of specific location'), establishing a baseline of 3. The description adds 'by GEO location' which aligns with the parameters but provides no additional semantic value regarding coordinate formats, precision requirements, or the significance of the provided default values.

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 demographics') and input method ('by GEO location'), but 'surround area' is vague (radius undefined) and it borders on tautology with the tool name 'propertiesget_demographics'. It fails to specify what demographic data is returned (population, income, etc.) or distinguish clearly from siblings like 'propertiesget_scores'.

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 like 'propertiesdetail', 'propertiesget_scores', or 'propertiesget_statistics_deprecated'. No mention of prerequisites, rate limits, or specific use cases where demographics data is preferred over other property data.

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