List the California codes and local ordinances available for lookup, and state honestly what is NOT covered. Call this before telling a user a code is unavailable, and when you need the exact document slug or jurisdiction slug for a lookup.
| Name | Required | Description | Default |
|---|---|---|---|
| jurisdiction | No | Optional. A California city or county slug — returns the documents held for that jurisdiction instead of the statewide list. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context by saying the tool honestly reports what is NOT covered and should be used before declaring a code unavailable, implying its negative results are authoritative. No contradiction with annotations.
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 with zero filler. The main purpose and scope are front-loaded, followed by precise call-timing guidance, making the description easy to scan and act on.
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 simple list tool with one optional parameter and rich annotations, the description is nearly complete: it explains purpose, usage timing, and the authoritative nature of the coverage list. It does not describe the output format, but the absence of an output schema and the simple list nature make this a minor gap.
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?
There is only one optional parameter and schema description coverage is 100%, so the schema already explains that jurisdiction is a city/county slug and changes the returned set. The description mentions needing the 'jurisdiction slug' but adds no meaning beyond the schema.
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 a specific verb and resource: 'List the California codes and local ordinances available for lookup.' It adds a clear boundary by noting the tool also states what is NOT covered, and the enumeration purpose is distinct from the sibling lookup_california_code_section tool.
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?
The description gives explicit when-to-use triggers: 'Call this before telling a user a code is unavailable, and when you need the exact document slug or jurisdiction slug for a lookup.' It does not name the sibling tool as the follow-up alternative, but the 'for a lookup' context makes the routing reasonably clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.