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

With annotations already marking readOnly and idempotent, the description adds valuable context: the catalog is static, does not check availability, and does not return a fixed price. This goes beyond the annotations to warn agents against using this tool for real-time pricing or availability. It does not mention pagination behavior, but the output schema covers the response.

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?

Two sentences with no wasted words. The first sentence front-loads the exact purpose and attribute list; the second adds the critical limitation and points to the correct alternative. Every clause earns its place.

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 read-only catalog discovery tool with an output schema, annotations, and a clear pointer to search_homes, this is quite complete. It could add a note about pagination or default result set, but nothing essential is missing for correct invocation.

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 only 11%, so the description must compensate. It does clarify several filters (name, public code, condominium, neighborhood, city, bedrooms, amenities) that map to query, neighborhood, city, minBedrooms, and amenities. However, it leaves maxGuests, language, page, and pageSize unexplained, and the 'query' parameter semantics are already in the schema.

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 a specific verb and resource: 'Read-only static catalog discovery' of Voya Homes properties, listing concrete search attributes (property name, public code, condominium, neighborhood, city, bedrooms, amenities). It also distinguishes itself from the sibling search_homes by explicitly stating it does not check date availability or return a fixed price.

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?

It gives an explicit when-not and alternative: 'use search_homes after selecting travel dates' for availability/pricing, implying this tool is for pre-selection catalog discovery. The condition is clear, and even though get_home/list_destinations are not mentioned, the main ambiguity is resolved.

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