Realty In Ca1 MCP Server

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

No annotations are provided, so the description carries the full disclosure burden. It fails to mention that this is a read-only operation, that results are paginated (max 50 records), or that mandatory geographic bounds are required. No information about rate limits or response structure is provided.

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 a single, efficient sentence with no redundancy. However, given the tool's complexity (27 parameters with mandatory geographic requirements), extreme brevity becomes a liability rather than a virtue, preventing necessary context from being conveyed.

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 27 filtering parameters, mandatory geographic bounds, and no output schema, the 8-word description is inadequate. It fails to mention the required coordinate parameters, available filters (price, building size, zoning), or any aspect of the return payload.

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, establishing a baseline of 3. The description adds no parameter-specific context (e.g., explaining that the required coordinates form a bounding box, or how the 'BuildingTypeId' values map to commercial property types), but the schema adequately documents individual fields.

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 action ('List') and resource ('commercial properties'), and distinguishes from the 'residential' sibling tool by specifying 'commercial'. The addition of 'both for lease and for sale' clarifies scope, though it could better differentiate from 'propertieslist_by_mls'.

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 scope ('both for lease and for sale') but fails to provide explicit when-to-use guidance versus alternatives like 'propertieslist_by_mls' or 'propertieslist_residential'. Critically, it omits that four geographic bounding box parameters are required to execute the search.

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