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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that it is 'interactive' and produces a visual card with photos and a 'Book now' button, which is behavioral context beyond annotations. No contradiction.

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 concise: two short paragraphs. The purpose and usage guidance are front-loaded, and every sentence earns its place. The pointer to check_availability avoids 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 the tool has no output schema and is a visual renderer, the description sufficiently covers what the agent needs to know: it renders a card with photos, prices, and a button. It defers parameter details to check_availability, which is fine in this sibling context. No critical information 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 0%, so the description must compensate. It explicitly says parameters are identical to check_availability and directs the agent there for full docs. This is a clear pointer, but it does not add any direct parameter meaning itself. It relies on the sibling tool, which is acceptable but not fully self-contained.

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 tool renders an interactive availability card for a specific property, and explicitly contrasts it with check_availability by noting it produces identical text output but adds visual elements. This directly differentiates it from sibling tools like render_apartment_gallery and render_rates_card.

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 explicit guidance: use this when the user wants to see apartments visually, typically after check_availability confirms availability. It even names the sibling and the sequence, so an agent knows exactly when to invoke it versus alternatives.

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