Check a site for favicon, apple-touch-icon, web app manifest, and theme-color presence — a quick completeness check for browser/OS chrome and PWA metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Any URL on the site to check (origin is derived from it) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the check only tests 'presence' of items, not validity, and that it is a 'quick' check. It does not reveal operational details such as how the URL is fetched, whether JavaScript-rendered content is considered, or what the return payload looks like; this is a moderate gap for a tool with no output schema.
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 22-word sentence with no filler. It front-loads the action ('Check a site for...') and the object list, and the context clause 'quick completeness check' adds useful scope without 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 check tool, the description sufficiently explains what is checked and implies a quick read-only audit. Non-obvious details such as output format are absent, but the schema fully documents the input and the tool's scope is narrow, so an agent can select and invoke it correctly with minimal ambiguity.
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, url, is fully described in the schema as 'Any URL on the site to check (origin is derived from it),' so schema coverage is 100%. The tool description does not add further parameter-level meaning, but it is unnecessary given the schema's clarity.
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 uses a specific action ('Check') and enumerates the exact resources examined (favicon, apple-touch-icon, web app manifest, theme-color). This distinguishes it from siblings like seo_audit or page_performance_check by targeting PWA/browser chrome metadata. The phrase 'quick completeness check' further clarifies it is a focused, non-exhaustive scan.
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 text implies a use case — checking PWA/browser metadata completeness — via 'quick completeness check for browser/OS chrome and PWA metadata.' However, it does not explicitly state when to prefer this tool over alternatives (e.g., seo_audit or page_performance_check) or provide when-not-to-use conditions. The intended context is clear but not formally contrasted with sibling tools.
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.
Many tools audit overlapping site signals (seo_audit vs structured_data_extract vs tech_stack_fingerprint; page_performance_check vs pagespeed_insights; ssl_cert_check vs ssl_labs_grade; broken_link_check vs sitemap_url_validator), so an agent could initially pick the wrong one. Descriptions usually clarify the distinction, but the boundaries are not always obvious.
Most names follow a snake_case target+operation pattern (ssl_cert_check, email_deliverability_check), but check_open_ports and check_robots_sitemap reverse the order, and the action suffixes vary widely (check, audit, validate, lookup, extract, grade, report, insights). Still readable, but not a single predictable convention.
At 29 tools, the server is above the 25-tool threshold and feels like an undifferentiated grab bag of single-purpose audits rather than a tightly scoped toolkit. Many checks could be consolidated (e.g. the separate SSL and performance tools, or domain_report versus its component checks).
For a web/domain/email/security diagnostics toolbelt, the coverage is unusually broad: DNS, TLS, email, SEO, structured data, vulnerabilities, ports, redirects, and more are all represented. Minor gaps exist (no generic HTTP request/debug tool, no zone-transfer or full WHOIS history), but agents can accomplish most diagnostic workflows without hitting dead ends.