search_municipal_code

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

No annotations provided, so description fully discloses behavior: returns top-matching chunks with section numbers, source URLs, and PDF anchors. Adequate for a read-only search tool; 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 wasted words. Purpose and usage are front-loaded. Highly efficient and clear.

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?

While output schema likely covers return format, the description omits parameter details, leaving agents to guess about limit, doc_types, and min_similarity. Incomplete for a 4-parameter tool with no schema descriptions.

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%. Description fails to explain any of the 4 parameters (query, limit, doc_types, min_similarity). Only query is implied via examples. Does little to help agent understand 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 it performs semantic search across San Diego Municipal Code, information bulletins, and ordinances. It distinguishes from sibling tools like get_code_section and get_bulletin, which are more specific lookups.

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 use cases with example questions ('what are fence height rules', 'when do I need historical review'), guiding when to use semantic search. Does not explicitly state when not to use, but context implies alternatives exist for exact matches.

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