Check the verification and backlink status of a CAN-TAP Verified directory listing. Returns whether the business is claimed, verified, and where the dofollow backlink lives. Use this after calling claim_listing to verify the dofollow link is active.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The business slug from a previous claim_listing response (e.g. 'joe-plumber-toronto') |
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 return values (claimed, verified, backlink location) and implies a read-only operation via 'check', but does not explicitly state side effects, permissions, or error behavior. The workflow reference to claim_listing adds some context.
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 two sentences, front-loaded with the core purpose, and contains no filler or redundant phrasing. Every sentence contributes meaning.
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?
Given the tool's low complexity (one parameter, no output schema), the description covers purpose, return values, and usage context sufficiently. It could explicitly state it is a read-only operation, but overall it is complete enough for an agent to select and invoke correctly.
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%, and the schema already describes the slug as coming from a previous claim_listing response. The tool description reinforces this but adds no new semantic detail beyond the schema, warranting the baseline score.
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 the tool's function: checking verification and backlink status of a CAN-TAP Verified directory listing. It specifies what is returned (claimed, verified, dofollow backlink location) and distinguishes itself from sibling claim_listing by referencing it as the preceding step.
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 explicitly tells the agent when to use this tool: 'Use this after calling claim_listing to verify the dofollow link is active.' This gives clear context, though it does not name alternative tools or exclusions, so it falls short of a 5.
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.