Get NFC tap and review analytics for a CAN-TAP Verified business. Returns total taps, positive vs concern split, average star rating, and recent activity. Use this for businesses that own a CAN-TAP NFC review stand.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Business slug |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of disclosure. It describes what the tool returns (total taps, split, rating, activity) and implies a read-only operation via 'Get,' but it does not explicitly state safety traits like no side effects or authorization requirements, so it provides modest behavioral 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 action and resource, and efficiently conveys purpose, return values, and usage context without unnecessary details.
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 simplicity (one parameter), lack of output schema, and the siblings' clear differentiation, the description adequately covers the return values (taps, split, rating, activity) and usage context. It is complete enough for an agent to understand what to expect.
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 schema already documents the single parameter 'slug' with 100% coverage, so the baseline is 3. The description does not add any additional parameter-specific meaning beyond confirming the tool is for CAN-TAP Verified businesses, which is contextual rather than parameter-level.
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 purpose with a specific verb ('Get') and resource ('NFC tap and review analytics'), and distinguishes it from sibling tools by focusing on business analytics. It also lists specific data points returned, making the purpose unmistakable.
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 by stating 'Use this for businesses that own a CAN-TAP NFC review stand,' which tells the agent when this tool is appropriate. However, it does not explicitly mention when not to use it or reference alternative tools, so it lacks full exclusion criteria.
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.