Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does well by disclosing the endpoint host, the exact monetary cost (0.002 USDC per call), the settlement chain (Base mainnet), and the automatic payment mechanism via PAYER_PRIVATE_KEY. It does not cover rate limits, failure behavior, or response structure, but the cost and auth details are substantial behavioral context that an agent needs before invoking.

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 that moves from the core action and return set to operational details (cost, chain, payment wallet). Every clause carries information the agent needs, with no filler.

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 one-parameter read tool with no output schema and no annotations, the description supplies the essential operational context: what it returns, where it calls, and the payment implications. It could add a note on error behavior or result shape, but nothing critical to correct invocation is missing.

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 has 100% description coverage for the single 'domain' parameter, so the baseline is 3. The description reinforces that exactly one domain is expected ('for one domain'), but adds no format or validation details beyond what the schema's example already provides.

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 verb and resource ('Fetch the full DNS record set for one domain') and enumerates the record types returned (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA). This clearly distinguishes it from siblings like domain_profile or website_intelligence, which do not advertise raw DNS record retrieval.

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 by saying it fetches records 'for one domain', but it does not explicitly state when to choose this over siblings such as domain_profile or site_check. There are no exclusions or alternative-selection guidance, leaving the agent to infer the appropriate context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden and it does disclose the critical non-obvious trait: a 0.01 USDC charge per call on Base mainnet, auto-paid from PAYER_PRIVATE_KEY. That monetary side effect is exactly the kind of thing an agent must know before invoking. It does not cover failure modes, rate limits, or whether a failed call is still charged.

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?

One dense sentence that front-loads the action and payload, then appends the payment constraint. No filler, nothing repeated from structured fields.

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?

With no output schema, the description must convey the return shape; it names the three sections but not their structure or whether subdomains are paginated/truncated. Cost and auth are covered, which is the more important gap for a paid tool, but return-format detail is thin.

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?

Single parameter with 100% schema description coverage and an inline example ('example.com'), so the schema fully documents it. The description adds nothing about the domain parameter itself; baseline 3 applies.

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?

States a specific verb+resource ('Fetch a domain profile') and enumerates the payload: registration basics, DNS summary, subdomains from certificate logs. This lets an agent see it overlaps with dns_lookup and website_intelligence but it never names those siblings to draw the line explicitly.

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?

No when-to-use guidance and no alternatives named, even though dns_lookup and website_intelligence in the sibling list clearly overlap in scope. The agent must infer from the payload list alone whether to call this or the narrower tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose the key non-obvious trait: a real monetary cost of 0.005 USDC per call on Base mainnet, auto-paid from PAYER_PRIVATE_KEY. It still omits failure behavior for non-feed URLs and any auth/wallet-missing error mode.

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?

Two compact sentences: purpose front-loaded, payment terms second. Every clause carries information and nothing is padded.

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 one-parameter tool with no output schema and no annotations, this covers what it does, what it returns in shape terms, and its billing model. Missing only edge-case behavior (invalid feed, payment failure) that an agent would want before calling.

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?

Only one parameter, and the schema already documents it at 100% coverage with an example URL. The description adds the useful constraint that the address should be a feed (RSS/Atom/RDF), but no extra format or validation detail beyond that.

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?

States a specific verb and resource: reading an RSS/Atom/RDF feed, normalized into dated items with summaries. The feed resource type naturally separates it from page_reader, but it never names that sibling explicitly.

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?

Usage is only implied by the term 'feed' in the parameter description. There is no explicit statement of when to prefer this over page_reader (e.g. feed URL vs arbitrary HTML page), and no exclusions or prerequisites beyond the payment note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description still discloses two operationally important traits: a fixed price of 0.002 USDC per call on Base mainnet and that payment is automatic from the wallet in PAYER_PRIVATE_KEY, so the agent knows invocation spends funds without further auth steps. It stops short of covering failure behavior, rate limits, or whether JavaScript-rendered links are captured.

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?

Two tight sentences, front-loaded with what is extracted and followed by the cost/payment constraint. The 'through api.sitesy.ca' provider mention is minor surplus but not wasteful.

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 one-parameter tool with no output schema, the description covers the essential unknowns: what is returned (internal/external links with anchor text) and the billing side effect. Only edge-case behavior (blocked pages, JS rendering, pagination) is missing.

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% for the single 'url' parameter, so the schema already documents it with an example. The description adds only that it is 'one web page' (singular, one URL per call), which is marginal added meaning.

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 gives a specific verb and resource ('Extract the links on one web page') plus the output shape (internal vs external, anchor text), which separates it from page_reader and page_metadata without naming them. It does not explicitly distinguish itself from those siblings, keeping it short of a 5.

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?

There is no guidance on when to call this versus page_reader, page_metadata, or sitemap, and no stated preconditions for the page being reachable or rendered. The only routing-relevant information is cost, not usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It does disclose two important traits: a fixed 0.002 USDC charge on Base mainnet and automatic payment via the wallet in PAYER_PRIVATE_KEY, which tells the agent about cost and auth setup. It says nothing about failure modes on unreachable pages, redirect handling, or caching, leaving real behavioral gaps for a network-fetching tool.

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?

Two sentences, zero filler, with the capability stated first and the cost/payment fact second. Every clause earns its place.

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?

No output schema exists, so the enumeration of returned fields is genuinely necessary and present. Cost and payment mechanism are covered. Minor remaining gap: no mention of what happens when a page cannot be fetched or when the wallet lacks funds.

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% for the single 'url' parameter, so the schema already carries the semantics. The description adds no constraint, format, or scope detail beyond what the schema's example provides, so the baseline of 3 applies.

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 verb-and-resource ('Fetch page metadata') and enumerates the exact fields returned (title, description, canonical, Open Graph/Twitter tags, icons, structured data types). It does not, however, distinguish itself from siblings like page_reader or website_intelligence, which an agent could reasonably confuse with metadata extraction.

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?

There is no statement of when to choose this over page_reader or website_intelligence, nor any exclusions. The only usage-relevant signal is the per-call cost, which implies 'use sparingly' but never says so explicitly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It usefully discloses the paid nature of the tool: 0.01 USDC per call on Base mainnet, paid automatically from the configured wallet. However, it omits error behavior, rate limits, payment failure handling, and return format details.

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 tight sentences with no wasted language. It front-loads the purpose and follows with the critical cost/payment detail.

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 one required parameter and no output schema. The description covers the core output concept and payment behavior, but without an output schema it does not explain the returned text/metadata structure or failure modes.

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 has 100% description coverage for the single URL parameter, so the baseline is 3. The description does not add syntax or format guidance beyond the schema's example URL.

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 verb and resource: extract clean readable text and metadata from one web page. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as page_metadata or website_intelligence.

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 gives no guidance on when to use this tool versus alternatives like page_metadata or website_intelligence. It implies the tool is for reading a single page, but there are no exclusions or alternative-routing instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does disclose the two traits an agent most needs before calling: a metered cost (0.001 USDC per call on Base mainnet) and automatic payment from PAYER_PRIVATE_KEY, which implies a funded-wallet prerequisite. It stops short of covering redirect-depth limits, timeouts, or failure behavior.

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?

Two sentences, zero filler, with the action and the hop-by-hop scope front-loaded and billing detail trailing. Every clause carries information.

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 one-parameter, no-output-schema tool, the description covers purpose and the notable cost/auth requirement, which is enough to call it correctly. Depth limits and return shape are the only unaddressed items, and the latter is partly excused by the absence of an output schema.

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 there is only one parameter, so the schema already fully documents 'url'. The description adds no format constraints or edge-case notes (max hops, whether the URL must be absolute), so it matches baseline rather than exceeding it.

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?

States a specific verb and resource ('Trace a web address') plus the mechanism ('hop by hop, reporting every status and destination'), which distinguishes it in spirit from dns_lookup and site_check. It never names a sibling explicitly, so an agent must infer the boundary rather than read it.

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?

Usage is only implied: follow redirect chains and report each hop. There is no statement of when to prefer this over dns_lookup, site_check, or page_reader, and no exclusions or preconditions beyond the payment note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it discloses important behavior: cost (0.001 USDC per call), network (Base mainnet), and that payment is automatic from the wallet in PAYER_PRIVATE_KEY. It does not cover response format, timeouts, redirect-following depth, or failure behavior, but the payment/auth disclosure is substantial context above the annotation baseline.

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?

Two sentences, front-loaded with the checks performed and followed by the cost/payment model. Every sentence earns its place; only the endpoint host 'api.sitesy.ca' is arguably extraneous detail, keeping it just below the top score.

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 one-parameter diagnostic tool with no output schema and no annotations, the description adequately covers what is checked and the payment mechanism. Missing is any hint of return shape or error handling, but the enumerated checks give the agent a reasonable expectation of the response content.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents the domain format with an example. The description adds no additional parameter semantics (no normalization rules, no protocol prefix handling), so the baseline 3 is appropriate.

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 names a specific verb ('Run') and resource ('quick site check') and enumerates exactly what is checked: HTTPS reachability, HTTP behaviour, certificate days remaining, security header presence. This is clear enough to distinguish it from most siblings, though it doesn't explicitly contrast with overlapping tools like dns_lookup or redirect_trace.

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?

'Quick site check' implies a fast, broad assessment, which gives some usage context, but there is no explicit when-to-use or when-not-to-use guidance, and no named alternatives among the many siblings. The agent must infer that this is the broad pre-flight option versus narrower tools like dns_lookup or page_reader.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose the most consequential trait: this is a paid call at 0.002 USDC on Base mainnet, settled automatically from the wallet in PAYER_PRIVATE_KEY. It does not say whether sitemap indexes are followed recursively, what happens when no sitemap exists, or error/rate-limit behavior.

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?

Two sentences, zero filler, and the action is front-loaded ahead of the payment caveat. Every clause carries information an agent needs.

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 one-parameter tool with no output schema, the description covers the data source, the returned content in loose terms, and the billing mechanism. The main remaining gap is return shape detail — whether index sitemaps are expanded or returned as-is.

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?

Only one parameter and schema description coverage is 100%, so the schema already explains 'domain' with an example. The description adds no syntax, normalization, or URL-vs-domain guidance beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: fetch a domain's sitemaps and list the page addresses they declare. This is clear enough to distinguish it from page_links or feed_reader, though it never explicitly contrasts with those siblings.

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?

Usage is only implied by the resource name — an agent can infer it is for discovering pages via sitemap. There is no statement of when to prefer this over feed_reader or page_links, and no exclusions or prerequisites beyond the payment note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does a good job: it discloses the exact information categories returned, the flat per-call cost, the network (Base mainnet), and the payment mechanism (automatic from PAYER_PRIVATE_KEY). It omits rate limits, error/failure behavior, and whether the upstream API needs its own credentials beyond the payer wallet.

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?

Three sentences, front-loaded with purpose, then return contents, then cost/payment. The middle sentence is a long enumeration but each item is a distinct datum the agent may care about, so there is little waste.

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 single-parameter read tool with no output schema and no annotations, the description covers what the report contains and the economic/payment side well enough to call it correctly. Minor gaps are error behavior and any latency or rate constraints.

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?

Only one parameter exists and the schema already documents it at 100% coverage with an example format. The description reinforces it with "for one domain" but adds no new syntax, normalization, or validation meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Fetch a website intelligence report for one domain") and enumerates the report's contents, so the agent knows exactly what comes back. It does not differentiate from overlapping siblings like domain_profile, dns_lookup, or site_check, which also surface DNS and security data.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of the alternatives (domain_profile, site_check, dns_lookup) that cover parts of the same ground. The cost note (0.01 USDC per call) implicitly signals this should not be called casually, which is useful but not a routing rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.