search_building_code

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

No annotations provided, so description carries burden. Clearly states the search domain and language requirement, which is sufficient for a read-only search tool. Does not mention output format but no contradictions.

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, no fluff, essential information front-loaded. Every sentence adds value: purpose and important usage rule.

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?

Lacks description of output format/return values, which is not covered by output schema (none). Given the tool's simplicity, a 3 is appropriate; could be improved by briefly mentioning what the search returns (e.g., list of articles).

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 description adds value by specifying query must be in Traditional Chinese and composed of core nouns, with examples. This goes beyond the schema's generic 'Search keyword in Traditional Chinese'.

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 it searches for official law articles in a specific code (Taiwan Building Code - Construction Works), with a specific verb 'search' and a well-defined resource. No ambiguity.

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 instructions: query must be in Traditional Chinese, extract 1-3 core nouns. No explicit when-not-to-use or alternatives, but the guidance is strong for correct usage.

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