turkey_real_estate_listings_scraper

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

No annotations are supplied, so the description carries the full behavioral burden. It does usefully disclose the returned content (listings, square-meter pricing, agent details), which partially substitutes for a missing output schema, but says nothing about data freshness, source portals, error behavior for unsupported city slugs, or cost/rate limits for a scraping operation.

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?

A single front-loaded sentence with the resource stated first and no wasted wording. It is tight and readable, though the brevity leaves no room for the usage or behavioral context that the absent annotations call for.

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?

All three optional parameters are fully documented in the schema and the description covers the extracted payload, so basic invocation is covered. However, for a scraper with no annotations and no output schema, an agent still lacks page/coverage limits, expected data shape, and failure modes for unknown cities or categories.

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%, so all three parameters (city, category, maxItems) are already documented with defaults and examples. The description adds only marginal framing — 'regional cities' reinforces the city scope and 'commercial' hints that category covers more than sale/rental — which does not exceed the schema baseline.

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 ('Extract') and specific resources (residential/commercial real estate listings, square-meter pricing, agent details) scoped to regional Turkish cities. An agent can tell exactly what domain this covers, and no sibling tool overlaps that domain, though the description never explicitly contrasts itself with them.

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?

There is no when-to-use guidance, no prerequisites, and no exclusions or alternatives named. The agent must infer from the name and description that this is the tool for Turkish property data, with nothing about when it should prefer another source or when it should not call it.

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