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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context beyond that: it performs the same lookup as get_apartment_details, produces identical text output, and renders an interactive visual card. No contradiction with 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 compact and front-loaded: purpose first, then usage guidance, then a short pointer for parameters. Every sentence earns its place and avoids duplicating what get_apartment_details already documents.

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?

With 2 optional parameters, read-only annotations, and no output schema, the description provides enough to call the tool correctly: when to use it, its relationship to get_apartment_details, and its visual nature. It is slightly reliant on get_apartment_details for parameter details, but that reference covers the gap.

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?

The input schema has 0% description coverage and only name/language with defaults. The description compensates by stating args are identical to get_apartment_details and pointing there for full docs, but it does not actually explain the parameters, leaving the definition dependent on another tool.

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: 'Render the interactive apartment gallery card' for a named property. It clearly differentiates from get_apartment_details by emphasizing visual presentation and from sibling render_* tools by specifying the gallery card and its visual contents.

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 explicitly says 'call this one when the user wants to SEE the apartment(s) visually' and places it after get_apartment_details confirms something worth showing. This gives a clear selection rule and names get_apartment_details as the text-output alternative.

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