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 value by disclosing that only available-now numbers come back and that results include price, tier, page URL and payment rules (transfer + delivery fee, down payment). It says nothing about result ordering, pagination or how limit interacts with the result set beyond the schema's max of 20.

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 resource and scope before listing filters; the parentheticals earn their place by decoding enums and Arabic terms. It is somewhat run-on and would read faster split into a purpose sentence and a filter sentence.

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 10-parameter optional-filter search with no output schema, the description covers purpose, filter semantics and the shape of returned data (price, tier, URL, payment rules) plus the availability constraint. Only ordering/pagination behavior is left implicit.

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?

With only 50% schema description coverage, the description compensates well: it decodes the pattern enum (triple/quad/penta/hexa = digit repeated 3/4/5/6+ times, mirror = ABBA ending, birth_year = ends with a year), clarifies that tier is Baqer's classification rather than the operator's, and gives examples for ending and prefix. Sort, limit and operator semantics remain unexplained, keeping it below a 5.

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 (search) and resource (special/VIP mobile numbers for sale at Baqer Store, Iraq) and names the two covered operators (Zain, Asiacell), which clearly separates it from search_products and get_product.

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 clear usage context: the filtering dimensions an agent can combine (operator, ending, contains, prefix, pattern, tier, price in IQD) and the constraint that only currently available numbers are returned. It does not explicitly say when to prefer this over the sibling search_products, so it stops short of full alternative routing.

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