get_readiness_scoreRivalSweeper 6-pillar AI/agent-readiness score for a domain (schema.org, technical access, content quality, trust, AI-specific, entity recognition) with tier and highlights. Uniquely RivalSweeper data. 1 credit; no data = no charge.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain to score |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description only mentions the one-credit cost and no-charge policy when no data exists. It omits behavioral details like error handling, rate limits, or idempotency, which is insufficient for a tool with zero annotation coverage.
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 concise sentences that front-load the core purpose and add only essential credit-related information without any fluff or redundancy.
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 one-parameter tool with no output schema, the description covers what it does and the cost model, but lacks specification of the output format (e.g., structure of score, tier, highlights) which would improve completeness.
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 only parameter 'domain' is described in the schema as 'Domain to score'. The tool description adds no further semantic detail (e.g., format, examples), so it meets the baseline for 100% schema coverage.
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 it computes an AI-readiness score using six specific pillars, and distinguishes itself from sibling tools by mentioning 'Uniquely RivalSweeper data' and the focused purpose.
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 usage when a general AI-readiness assessment for a domain is needed, but lacks explicit when-to-use or when-not-to-use guidance compared to sibling tools like get_brand_snapshot or get_competitor_price.
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 aspect of competitive intelligence: coverage, snapshot, price, history, promotions, readiness, and monitoring request. There is no overlap or ambiguity.
Most tools follow a 'get_' prefix pattern, but 'request_monitoring' uses 'request_'. This slight inconsistency is justified by the different action type (request vs. retrieve), but still deviates from the predominant convention.
With 7 tools, the set is well-scoped for a competitive intelligence server. Each tool serves a distinct need without being overwhelming or too few.
The tools cover the main competitive signals: snapshot, price, history, promotions, readiness, and domain monitoring. Minor gaps like listing all monitored domains are absent, but the core workflows are complete.