Text-search NorthPoint's signal feed for a keyword or phrase across competitor/regulatory/narrative entries.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Lookback window in days (default 30, max 365). | |
| query | Yes | Free-text query — matches title, body, subject, tags. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden for behavioral disclosure. It indicates a text-search operation but does not disclose return format, result limits, pagination, or whether the operation is read-only beyond the inherent nature of a search.
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 filler words. Every part contributes to defining the tool's purpose and scope.
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?
The tool is simple with only two parameters, but there is no output schema and no annotations. The description covers the search action and scope but neglects to state that it returns matching signals or any details about the response, leaving an agent to infer the return behavior.
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 100% for both query and days parameters. The tool description adds context about searching across signal categories but does not elaborate on parameter syntax or behavior beyond the schema, so it meets the baseline without adding significant value.
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 action ('Text-search') on a defined resource ('NorthPoint's signal feed') and scopes the search to 'competitor/regulatory/narrative entries.' This clearly distinguishes it from siblings like get_latest_signal, which retrieves rather than searches.
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 implies when to use the tool—when a keyword or phrase needs to be found in the signal feed. However, it does not explicitly state when not to use it or mention alternative tools, so it lacks the full exclusion/alternative guidance.
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.
Each tool targets a distinct resource or action: signal retrieval, search, ruleset listing, and regime-specific audits. The run_*_pro_check tools are parallel but clearly differentiated by jurisdiction names, and get_latest_signal vs search_signals serve different purposes.
All tool names follow a consistent verb_noun pattern with lowercase and underscores. The verbs get, list, search, and run are used predictably, and the run_*_pro_check pattern is uniform across all audit tools.
13 tools is well within the ideal 3-15 range and each tool earns its place for a marketing compliance server. The count covers discovery (list_regimes), free resources (get_lite_ruleset), signal monitoring, and comprehensive audits across multiple jurisdictions and specialized checks.
The tool set provides thorough coverage of the marketing compliance domain: free ruleset for self-audit, full pro checks for major regulatory regimes (EU, UK, US, Singapore, UAE), specialized audits for ad creative, AEO visibility, and TGE readiness, plus signal feed access and search. No obvious gaps or dead ends exist.
