khda_search_school

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

No annotations are provided, so the description must cover behavioral traits. It only says 'search' without indicating it's read-only, nor does it mention authentication, rate limits, data freshness, or any side effects. The bare description lacks transparency.

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?

Description is a single sentence of 9 words, front-loading the action. It is efficient with no wasted words, though slightly more context (e.g., 'substring match') could be included without harming conciseness.

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?

Given the presence of an output schema, return values need not be described. However, the description is minimal and does not clarify search behavior (substring vs exact match) or the relationship to sibling tools. It is adequate but not complete.

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%, so each parameter is already documented. The description adds no extra meaning beyond listing parameter types (name, area, curriculum, rating, fee). Baseline score of 3 is appropriate.

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?

Description clearly states the tool searches Dubai private schools by name, area, curriculum, rating, or fee. Verb 'search' and resource 'Dubai private schools' are specific, and the listed filtering dimensions distinguish it from sibling tools like khda_list_areas and khda_list_curricula.

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?

The description implies usage for searching schools with given filters but provides no explicit guidance on when to use this tool versus alternatives (e.g., khda_list_areas for area lists). No when-not-to-use or exclusions are mentioned.

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