Search the CAN-TAP Verified directory of 3,000+ real Canadian businesses by name, city, trade, or any combination. Returns matching listings with their URLs and claim status.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | Filter by city | |
| query | No | Free-text search across business names | |
| trade | No | Filter by trade category |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that results include URLs and claim status, and implies a read-only search operation. However, it does not describe the output format (e.g., list vs single object), pagination, or behavior when no matches are found, leaving some behavioral gaps.
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?
The description is a single, front-loaded sentence with no wasted words. It covers the main purpose and the return value efficiently, making it easy for an agent to quickly grasp the tool's function.
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 3-parameter search tool with no output schema or annotations, the description covers the essential context: what is searched, the filter dimensions, and what is returned. While it lacks details on pagination or result limits, these are not critical for basic usage and the description is otherwise complete.
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?
The input schema has 100% coverage for all three parameters, so the baseline is 3. The description adds value by explicitly stating that the parameters can be used in any combination, clarifying the relationship between query, city, and trade beyond the individual descriptions in 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 clearly states a specific action ('Search') and a specific resource ('CAN-TAP Verified directory of 3,000+ real Canadian businesses'), and mentions the return value (listings with URLs and claim status). This distinguishes it from sibling tools like check_backlink_status and claim_listing.
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 provides clear context for when to use the tool (searching businesses by name, city, trade, or combination) but does not explicitly name alternatives or exclusion criteria. Sibling tools are present but not referenced, so the guidance is clear but not exhaustive.
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.
Most tools are clearly distinct: search_directory and list_free_backlinks both return listings but one is general search and the other specifically lists claimable backlink opportunities, which could cause some confusion. The other tools (claim_listing, check_backlink_status, get_business_stats) are unambiguous.
All tool names follow a consistent verb_noun pattern with snake_case (search_directory, claim_listing, check_backlink_status, list_free_backlinks, get_business_stats). The verbs are clear and the naming style is uniform throughout.
Five tools is an appropriate scope for a directory/backlink service. Each tool serves a distinct purpose in the core workflow: search, list opportunities, claim, verify, and get stats. No tool feels redundant, and the set is easy to grasp.
The tool set covers the main workflow: finding backlink opportunities, claiming listings, and verifying the backlink. The addition of search_directory and get_business_stats provides useful supplementary functions. Minor gaps exist, such as no tool to update or unclaim a listing, but these are not critical for the stated purpose.