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 disclosure burden but reveals nothing about pagination behavior (despite explicit paging parameters), result limits, rate limiting, or what data structure is returned. The agent must infer behavior solely from parameter names.

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?

While brief (5 words), it is under-specified rather than efficiently concise. 'With options and filters' wastes space without conveying meaningful constraints. Key information (pagination, searchable fields) is not front-loaded.

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 14 filter/sort parameters, localization support, and pagination, the description is inadequate. With no output schema and no annotations, it should at least mention the searchable/filterable nature and paginated results to guide agent usage.

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 baseline applies. The description vaguely alludes to 'options and filters' but adds no semantic value beyond the comprehensive schema documentation (e.g., doesn't explain the relationship between paging parameters or sorting logic).

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 ('List agents') but adds tautological filler ('with options and filters') that restates the obvious existence of parameters. It fails to distinguish from sibling 'agentsdetail' or clarify scope (e.g., whether this returns basic info or full records).

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 'agentsdetail' for retrieving specific agent information, or when to apply filters versus retrieving unfiltered lists. No prerequisites or exclusion criteria mentioned.

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