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 fully covered elsewhere. The description adds no behavioral context of its own — nothing about how matching works (substring vs exact vs Hebrew/English synonyms), result size, or ordering. It restates purpose rather than disclosing behavior.

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 well-formed sentence with the entity and the filter front-loaded; nothing is wasted. It is arguably too terse rather than padded, which is penalized under other dimensions rather than this one.

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 one-optional-parameter read-only search with rich annotations and no output schema, the description is adequate but leaves a meaningful gap: whether the filter is optional and how it matches values, which directly affects how an agent should call it.

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 parameter already carries its meaning plus Hebrew/English examples, so the baseline is 3. The description's "by specialization" merely echoes the parameter name and adds no matching semantics 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?

States a specific verb ("find") and a specific resource ("career experts, consultants, and coaches on DrushimAvodot"), which cleanly separates it from the sibling search_jobs/search_courses/search_events tools by entity type. It stops short of explicitly naming those siblings or the boundary between 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?

Usage is implied only: query this when you want experts filtered by a specialization. There is no explicit when-to-use/when-not guidance, and notably no mention of what happens when the optional specialization is omitted (the schema shows 0 required params, so an unfiltered search is possible but undocumented).

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