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

Annotations already declare a safe read (readOnlyHint true, destructiveHint false, openWorldHint false). The description adds real behavioral context beyond that: the disambiguation behavior when one website hosts several properties, and an explicit enumeration of returned data. No output schema exists, so this return disclosure carries genuine weight.

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?

Front-loaded with the purpose, then inputs, then returns, then the edge case. The list of returned fields is long but justified because there is no output schema to carry it. Slightly dense but no wasted framing.

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 single-parameter read tool with annotations and no output schema, the description covers purpose, accepted inputs, return payload, and the multi-property edge case. Only the relationship to sibling lookup tools is left unaddressed.

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 coverage is 100%, so the baseline is 3, but the description goes further by enumerating accepted input shapes (site address, full URL, bare site name, host domain) that the terse schema example does not fully spell out.

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?

States a specific verb (look up) and resource (vacation rental) and explains the two lookup paths clearly. It does not, however, distinguish itself from the sibling get_property, which an agent might reasonably confuse it with.

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?

Gives implicit guidance through the accepted input forms and the multi-property candidate case, but never states when to prefer this over get_property or get_quote, nor the intended workflow (resolve site → then fetch details).

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