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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable non-obvious behavior: no authentication required, no browser automation, no proxy needs, and per-call pricing ($0.02). It also clarifies that currency is seller-set (GEL or USD), going beyond basic read-only framing.

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 only two sentences, yet it packs the core purpose, source, scope, currency behavior, access constraints, and pricing. Every clause earns its place; it is front-loaded with the primary function and includes no filler.

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 rich schema and annotations, the description provides enough context for an agent to select and invoke the tool. It lacks a description of the output shape (since no output schema exists), but the phrase 'real-estate listings' combined with known parameters like price and city gives reasonable expectations. A brief mention of returned fields would make it more complete.

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 100%, with all four parameters (city_id, deal_type, max_items, max_pages) already documented in detail. The description only mentions 'by city' and currency, which partially overlaps with the schema but adds no new parameter-specific meaning beyond what the schema provides.

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's function with a specific verb ('Pull'), the exact resource ('SS.ge'), and geographic scope ('Georgia's biggest real-estate classifieds portal'). It distinguishes itself from siblings by naming the unique site and location, making it unmistakable which tool to use for Georgian listings.

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?

The description gives clear context: it pulls live listings by city with seller-set currency, and explicitly notes 'No login, no browser, no proxies.' While it doesn't name alternative tools for other countries, the strong SS.ge branding makes the intended use obvious, though an explicit 'use for Georgia' comparison would improve it.

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