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

Annotations already disclose readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds scope context (Bulgaria, sale/rent, filters) but no additional behavioral details like pagination behavior, result limits, or defaults. There is no contradiction with the 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 English portion is front-loaded and compact, containing the core purpose and usage trigger. The Bulgarian translation is redundant but not harmful and may aid users of the Bulgarian market context.

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 16-parameter search tool with no output schema, the description covers the high-level purpose and when to call it. It does not describe result shape, pagination, sorting, or default behavior for transaction and currency, though some of that is partially covered by the input schema.

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 about 50%, and the description lists filter categories (city, neighborhood, price range, rooms, area) that map to parameters. It does not explain undocumented parameters like page, sort, limit, price_min/max, area_max, rooms_max, or furnished, leaving some semantics to inference.

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+resource: search real estate listings in Bulgaria, with explicit examples of property types and filter dimensions. It clearly covers the main search intent, but it does not explicitly name or contrast sibling tools like get_property or get_price_stats.

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 provides an explicit trigger: 'Use this whenever a user asks to find a home, apartment, house or property in Bulgaria.' However, it does not mention when not to use it or point to alternatives such as get_price_stats, get_property, or subscribe_to_search.

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