search_within_kanun

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

No annotations provided, so description carries full burden. Describes two search modes and their behavior, including Boolean operators and semantic embeddings. Lacks details on potential side effects, auth needs beyond API key, or rate limits, but adds value beyond schema.

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?

Structured into clear sections (modes, examples) with no redundant text. Every sentence adds value: two sentences covering core purpose, then bulleted lists for modes and examples.

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?

Covers both search modes, required parameters, optional parameters with defaults, and output schema exists. The description is complete given the tool's complexity and richness of schema and output schema.

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?

Input schema has 100% coverage with good descriptions. The description adds context by explaining modes and providing examples, which enhances understanding beyond the schema. However, the schema already handles parameter semantics adequately.

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?

Clearly states it searches within a specific law's articles using keyword or semantic search. Distinguishes from sibling tools like 'search_within_kanun' vs general 'search_kanun' by specifying 'within a specific law' and providing two distinct search modes.

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 explicit usage guidance for both keyword and semantic modes, including examples and noting the OPENROUTER_API_KEY requirement for semantic search. However, does not explicitly state when to choose this tool over siblings or when not to use it.

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