Zillow56 MCP Server

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

No annotations are provided, so the description carries full burden. It states 'Get' implying a read operation, but lacks details on behavioral traits such as authentication needs, rate limits, pagination behavior (implied by 'page' parameter but not explained), or what happens with invalid zuid. The description is minimal and doesn't compensate for missing annotations.

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 zero waste. It's front-loaded with the core purpose, making it easy to parse quickly. Every word earns its place without redundancy.

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 no annotations and no output schema, the description is incomplete for a tool with parameters. It doesn't explain what 'reviews' entail (e.g., content, format), how pagination works, or error handling. For a read operation with potential complexity, more context is needed to guide 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?

Schema description coverage is 100%, so the schema documents both parameters (zuid and page). The description adds no meaning beyond the schema, as it only mentions 'zuid' without explaining its format or purpose. With high schema coverage, the baseline is 3, but no extra value is provided.

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 ('Get') and resource ('agent reviews'), specifying retrieval by 'zuid'. It distinguishes from siblings like 'agent_details_by_username' by focusing on reviews rather than general details, but doesn't explicitly contrast with 'search_for_agents' or other review tools (e.g., 'buildersreviews_builders_reviews').

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 on when to use this tool versus alternatives is provided. It doesn't mention when to choose it over sibling tools like 'search_for_agents' or 'agents_active_listings', nor does it specify prerequisites or exclusions (e.g., requires a specific zuid format).

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