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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond that: free-form natural-language input in BG/EN/RU and what comes back (matched services, short description, page URL, starting prices from the official price list, phone number). It does not disclose match limits or what happens when nothing matches.

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?

Front-loaded with the trigger condition and the 'FIRST' directive, then examples, then return shape — a sensible information order. The problem list is long but each term is a real matching cue rather than filler; the closing sentence about return values partially duplicates what the output schema already conveys.

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 two-parameter, read-only matching tool with a full schema and an output schema, the description supplies everything an agent needs: trigger conditions, acceptable input language, and a summary of the response. Remaining unknowns (match count, no-result behaviour) are minor and partly inferable from the output 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 coverage is 100% and both parameters are already well documented in the schema, including examples and the language enum with a default, so the baseline of 3 applies. The description corroborates that the input is the problem in the user's own words, but adds no extra constraint or format detail and never mentions the language parameter explicitly.

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?

Names a concrete action (match a described home problem to services) plus a geographic scope (Varna, Bulgaria), and positions itself as the entry point with 'Call this FIRST'. The dense list of concrete problem examples (blocked drain, burst pipe, boiler, insurance report) leaves no ambiguity about what triggers it versus browsing siblings like list_services.

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?

Gives an explicit when-to-use rule ('when a user describes a home problem or need in or near Varna') backed by a rich trigger vocabulary, and the 'FIRST' instruction establishes ordering. It stops short of naming alternatives, e.g. deferring to check_service_area for out-of-area checks or get_prices for pure price enquiries.

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