School and public holidays

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral details beyond the schema, such as data coverage limitations or how conflicts between place and year are resolved. No contradiction with annotations exists.

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?

The description is a single, compact sentence that front-loads the core resource and its main scoping dimensions. Every word earns its place, and there is no redundant restating of the title or parameter names.

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 read-only query tool with a rich output schema and complete parameter documentation, the description is sufficient for selection and invocation. A minor gap is that it does not clarify whether 'place' only applies to school holidays or also to public holidays, but this is not critical given the schema context.

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?

The schema covers 100% of parameters with detailed descriptions, so the baseline is 3. The description adds only a slight mapping by saying 'canton or municipality' for place and 'public holidays' for kind, which is already reflected in the schema text. No new semantic meaning is added.

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?

The description states the resource (school/public holidays) and the key scoping dimensions (place, year), which clearly distinguishes it from all sibling tools. It lacks an explicit verb like 'get' or 'list', but the intent is unmistakable and the title reinforces the subject.

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?

There is no explicit guidance on when to use this tool versus alternatives, or any exclusions. The use case is implied by the name and description, but the description does not state 'use this when the user asks for holidays' or mention any sibling it replaces or complements.

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