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

Annotations already cover read-only/open-world safety, and the description adds real context beyond them: the propertyRef must be signed, and search results carry name, position, and propertyRef. It omits error behavior for an expired/invalid ref and any pagination or size limits on the returned photos/amenities.

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?

Three short sentences, front-loaded with what is returned, then the blocking precondition. No filler or restatement of the tool name.

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 two-param read tool with no output schema, the description covers the return contents and the critical prerequisite. The only real gap is the undocumented currency parameter, which an agent would have to infer from the schema's name and default.

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 0%, so the description must compensate. It explains propertyRef well (signed, sourced from search results, not a name), but says nothing about the currency parameter or its USD default, leaving one of two params undocumented everywhere.

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?

Specific verb+resource: returns photos, amenities, and property facts for a furnished home. It also scopes the input to a home 'selected from search results,' which implicitly chains it after search_stays, but it never names get_home_offers or get_hotel_details to sharpen the distinction among siblings.

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 states the precondition clearly (must come from search results, must have the signed propertyRef, a name alone is insufficient) and says where to get the ref. It stops short of naming alternatives or saying when-not to use it versus the offers/hotel siblings.

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