zurich_find_school_data

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

Annotations already indicate read-only, open-world, idempotent, and non-destructive behavior. The description adds behavioral context by mentioning it uses a curated combination of search terms and returns a Markdown list, providing value beyond 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?

Two concise paragraphs plus a return type line. Every sentence adds value; no fluff or repetition. Front-loaded with the core purpose.

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 a single optional parameter and an output schema (not shown), the description covers the main purpose, returns format, and search methodology. Could mention pagination or result limits but is largely complete for a focused search tool.

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 0%, meaning the tool description does not explain the 'topic' parameter. Although the schema itself describes the parameter with examples, the description fails to compensate for the low coverage, offering no semantic addition for the parameter.

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 it finds datasets relevant to the school board and primary schools. It uses specific examples like school facilities, education data, district school boards, student statistics, school routes, and related topics, differentiating it from general search tools like zurich_search_datasets.

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?

Implies usage for school-related data search but provides no explicit guidance on when not to use it or how it compares to alternatives like the general search tool. Lacks exclusion criteria or context for using this over zurich_search_datasets.

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