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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful nuance that these are asking (not transaction) prices and are broken down by property type with a Berlin comparison and trends, but discloses nothing about rate limits, auth, or freshness beyond 'Aktuell'.

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 dense sentence that front-loads the core resource (Quadratmeterpreise) and then layers scope and return content. No filler or 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?

For a read-only, single-parameter tool with full schema coverage and no output schema, the description usefully conveys what comes back: apartment vs. house prices, a Berlin benchmark, quarterly figure, and annual trend. It is nearly complete, missing only explicit sibling differentiation and recency details.

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% and the single 'area' parameter is fully documented with examples ('Zehlendorf', 'Prenzlauer Berg', 'Falkensee'). The description only reinforces the scope ('Berliner Ortsteil oder Umland-Ort') without adding syntax or format detail beyond the schema.

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 — 'Aktuelle Angebots-Quadratmeterpreise' — and scopes it to 'Wohnungen und Häuser getrennt' for a Berlin district or surrounding town. The purpose is unmistakable. It does not, however, explicitly distinguish itself from overlapping siblings like get_market_overview or get_bodenrichtwerte.

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?

Usage is only implied: an agent can infer this returns area-level asking prices, but the description never says when to prefer it over get_market_overview, get_bodenrichtwerte, or get_property_details. No when-to-use or when-not-to-use guidance is provided.

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