sok_skole

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

No annotations provided. Description implies read-only behavior (search, return list) but does not explicitly state destructive safety or auth requirements. It mentions the return is a compact list, which is helpful, but lacks deeper behavioral context like pagination or rate limits.

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 sentences only, maximum information density, front-loaded with primary action. No unnecessary words.

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 no output schema, the description adequately describes the return (compact list) and directs to sibling for details. It covers filtering and defaults. Missing mention of pagination or result limits, but acceptable for a 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 coverage is 100%, but the description adds valuable details not in the schema: case-insensitive navn filter, normalization of kommunenummer (leading zero, handling '301'), and default for type (alle aktive skoler). This aids correct parameter usage.

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 clearly states 'Søk etter skoler i en kommune' with specific verb and resource, and distinguishes from sibling tools by noting that 'hent_skole' provides details. It also differentiates from the barnehage siblings by tool name and context.

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?

Provides clear context: filters by name and type, returns compact list, and explicitly recommends 'hent_skole' for detailed info. No explicit when-not guidance, but the alternative is clearly stated.

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