IANA Zones

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

With no annotations, the description carries the transparency burden. It adds one useful behavioral detail, 'Page content is not stored', but omits other relevant behavior such as whether a live network request is made, redirect handling, error behavior, and how the json or zone parameters affect execution.

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 with the core output front-loaded and a useful privacy note second. There is no 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?

The tool accepts four optional parameters and has no output schema, but the description only addresses url behavior. It ignores the host, json, and zone parameters and does not explain how the tool relates to its many siblings, leaving an agent under-informed for both selection and invocation.

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%, so the baseline is 3. The description adds no parameter-level meaning beyond the URL case and does not compensate for any schema gaps because there are none.

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 concrete action ('Return') and specific outputs (host, scheme, HTTP status) for a URL. It is clear about the core function, but it does not explicitly distinguish itself from overlapping siblings like normalize-url or status-catalog.

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 phrase 'for a URL' implies when the tool might be useful, but there is no explicit guidance on when not to use it or how it differs from alternatives such as normalize-url, validate-json, or status-catalog. No exclusions or alternative-selection conditions are given.

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 disclosure burden; it does add one useful behavioral trait ('No identifiers are retained') and implies ephemeral processing. However, it does not disclose whether network requests are made, whether processing is read-only, or what side effects if any exist.

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 compact and has no filler, but the first sentence is too vague to justify its place. The privacy statement in the second sentence is the only concrete 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?

Four optional parameters and no output schema leave a lot unstated: the classification categories, expected output shape, and which parameter(s) to supply. The description is not complete enough for an agent to invoke compatibility with confidence, especially given the overlapping sibling tools.

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%, so the baseline is 3. The description adds no parameter semantics beyond what the schema already offers, but it does not need to compensate because the schema fully documents each optional field.

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 says only 'Show how this request is classified,' which is too vague to convey what the compatibility tool actually classifies or what schema applies. It does not name the resource or classification scheme, and the phrasing could fit several siblings without distinction.

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 guidance on when to use compatibility instead of citation, validate-json, domain-shape, or normalize-url. Both the tool and its alternatives remain ambiguous for the same task.

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 of behavioral disclosure. It only states a negative property (no WHOIS/ownership data) and does not mention side effects, input handling, validation behavior, or return format. Significant behavioral gaps remain.

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 clear sentence with no wasted words. It is front-loaded and easy to parse, though it sacrifices useful detail for brevity.

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 tool with four optional parameters and no output schema, the description is incomplete. It does not clarify what happens when multiple parameters are supplied, whether json is truly discarded, or how zone and url relate to the hostname-splitting operation.

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%, so the baseline is 3. The description adds no parameter-level meaning, but the schema already documents each field adequately.

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: split a hostname into labels. It also distinguishes the tool from WHOIS/ownership-related tools by explicitly excluding that data. However, the description does not clearly accommodate all four input parameters (url, json, zone), so the scope is not fully aligned with the schema.

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 guidance is given on when to use this tool versus alternatives, and no sibling comparison or exclusion criteria are present. The description implies a narrow use case (splitting hostnames) but does not explain how the other parameters fit or when each is appropriate.

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 provided, the description carries the full burden of describing behavior. It does not say whether the tool returns a list, accepts inputs, has side effects, requires authentication, or what happens with the provided url, host, json, or zone parameters. The noun-phrase description gives an agent no behavioral contract.

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 short sentence with no wasted words. However, the lack of a main verb makes it under-specified rather than genuinely concise; adding an action such as 'List the common IANA timezone names for clock calls' would improve structure without adding bulk.

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?

There are no annotations and no output schema, so the description must supply more context. It does not explain the return format, how the four input parameters relate to the tool, or how this tool fits with sibling timezone and clock tools. An agent cannot reliably know how to invoke it correctly.

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%, so the baseline is 3. The description adds no parameter-level meaning and does not explain why url, host, and json appear for an IANA timezone names tool, but each parameter is individually documented in the schema.

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 the resource (common IANA timezone names) and a context (clock calls), but it lacks a verb and never states whether the tool lists, returns, validates, or normalizes those names. It is less tautological than a one-word definition, but it remains vague and does not clearly differentiate from siblings like timezone or utc-time.

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 phrase 'for clock calls' implies a usage context, but there is no explicit guidance on when to prefer this tool over alternatives such as timezone or utc-time. It also gives no exclusions, prerequisites, or examples of when not to use it.

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 provided, the description must carry the behavioral disclosure burden. It only says the tool fetches a public robots.txt and returns counts, but does not mention network behavior, failure modes, response format, or that json and zone appear irrelevant to the stated operation. This is a meaningful transparency gap for a network-fetch 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?

The description is one sentence with no filler and front-loads the action. Every word contributes to stating what the tool does, making it highly concise.

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 no output schema, no annotations, and four optional parameters that seem mismatched, the single sentence is insufficient context for correct invocation. The description lacks input semantics, return format expectations, error behavior, and any indication of how the tool relates to sibling tools.

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%, but the parameter descriptions do not align with the robots.txt purpose: url is described as 'HTTPS URL to normalize or cite', json as 'JSON text to validate', and zone as 'IANA timezone name'. The description adds no mapping from these four optional parameters to the fetch operation, so an agent cannot confidently determine which parameter to populate.

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 ('Fetch') and resource ('public robots.txt') and states the output scope ('group counts only'), so the basic purpose is clear. It doesn't explicitly differentiate from siblings like domain-shape, but the name reinforces the purpose. However, the input schema's parameter descriptions ('normalize or cite', 'JSON text to validate') are unrelated to robots.txt, which slightly weakens purpose clarity.

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 guidance is given for when to use inspect-robots instead of alternatives such as domain-shape or status-catalog. The only implied context is fetching a public robots.txt, but the description does not state whether to pass a base host or a full URL, nor whether json or zone parameters should be ignored.

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 does disclose a real behavioral trait: 'Query and fragment are dropped.' However, it does not describe error handling, URL format requirements, or the effect of passing host/json/zone alongside url.

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 short sentences with no filler or repetition. The key behavior is front-loaded in the first sentence, and the second sentence adds a precise detail about query/fragment handling.

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 has four optional parameters, no output schema, and no annotations, so the description must carry significant context. It does not explain why host/json/zone exist, how the output is structured, or what happens on invalid URLs, leaving an agent uncertain about correct invocation.

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%, so the baseline is 3. The description adds some meaning for the url parameter by defining the normalization behavior, but it does not clarify how host, json, or zone relate to the operation and uses 'host' as an output concept rather than an input parameter.

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 operation and resource: 'Return origin, host, and path for a URL.' It is not a tautology and clearly describes URL normalization behavior. However, it does not clarify the exact output representation (single string vs. separate fields) or acknowledge that the input schema includes unrelated optional parameters.

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 no guidance on when to use this tool versus alternatives, no conditions, and no exclusions. Usage is only implied by the operation name and text, and no mention is made of the non-URL parameters in the schema.

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 of explaining behavior. It only states what the catalog is, not what invoking the tool does, whether it reads or mutates data, or what the output will look like.

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 short and front-loaded, with no wasted words. However, the single sentence is mostly a tautology and does not provide the operational information needed to use the tool correctly.

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 has no annotations, no output schema, four heterogeneous parameters, and many sibling tools, but the description provides none of the needed invocation context, return-value information, or usage criteria. This is far too incomplete for an agent to use the tool reliably.

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%, so all parameters have descriptions in the input schema itself. The tool description adds no parameter-level meaning and, more importantly, does not explain how these parameters relate to the catalog or to each other.

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 is essentially a restatement of the tool name: 'status-catalog' is rephrased as 'catalog of common HTTP status codes'. It lacks a verb and operation, and it does not explain why the input schema contains url, host, json, and zone, which are unrelated to a simple status-code catalog.

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 use this tool or how it relates to sibling tools like normalize-url, validate-json, or timezone. An agent has no basis for choosing this tool over alternatives.

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 for behavioral disclosure, but it only says what the tool returns. It does not explicitly state that the operation is read-only, how invalid timezone names are handled, or what the output format looks like.

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 or repetition. Every word contributes to the stated purpose, making it an excellent example of conciseness.

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 absence of annotations and output schema, plus a four-parameter schema containing several unrelated fields, the description is too thin to support confident invocation. It should at least state that only zone is used and indicate what the response contains.

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?

Even though the schema has 100% description coverage, three of the four parameters (url, host, json) are unrelated to the stated purpose of returning the current time in a timezone. The description does not clarify that only zone is relevant, and it does not warn that zone is effectively required despite being formally optional.

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 clear verb and resource: it returns the current time for a named IANA timezone. It is specific enough to understand the core purpose, but it does not differentiate from sibling tools such as citation, normalize, or validate.

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 about when to choose this tool over alternatives. The only hint is the implied use case of wanting the current time in a named timezone; no alternatives, exclusions, or conditions are mentioned.

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 must carry the behavioral disclosure burden, but it only states a noun phrase. It does not mention that the tool accepts no relevant parameters, that all 4 schema properties are ignored, what format the timestamp is returned in, or whether the call could have side effects. This leaves important behavioral traits undisclosed.

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 extremely concise and front-loaded, with every word contributing to the core purpose. However, it is arguably too sparse given the misleading parameter schema, and a single clarifying sentence about parameters would make it more useful. Still, as pure brevity, it is effective.

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 has a simple purpose but an unexpectedly rich schema with 4 unrelated properties, and no output schema exists. The description does not explain how to use the tool correctly (e.g., call with no arguments), what the return value looks like, or why the listed parameters exist. An agent would be uncertain about the correct invocation.

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 input schema provides 100% description coverage for all 4 parameters, so the baseline is 3. The description adds no parameter-level meaning and does not clarify why URL, host, JSON, or zone fields appear in a UTC timestamp tool. That mismatch reduces potential value, but the schema itself already documents each property adequately.

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 identifies the tool's output as the current UTC timestamp, which is concise and unambiguous. It does not use a verb like 'returns' or 'gets', but the intent is obvious. It does not explicitly differentiate from sibling tools like 'timezone' or 'iana-zones', but the UTC specificity provides some distinction.

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 such as 'timezone' or 'iana-zones'. There are no usage examples, exclusions, or conditions. A user might infer that it is for UTC time, but no explicit routing advice is provided.

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 are provided, so the description carries the burden of disclosing behavior. It does add one useful behavioral fact—'The body is discarded'—but it does not explain what the tool returns, whether it performs network calls, or how url/host/zone relate to validation.

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 short sentences with no filler. The main purpose is front-loaded and the behavioral note is concise. Every word 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?

The tool is low complexity, but the description leaves important gaps: no return format, no mention of how the validation result is expressed, and no clarification of why three unrelated optional parameters exist. The schema helps, but the description alone is not fully complete.

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%, so the baseline is 3. The description contributes essentially no additional parameter meaning; it does not explicitly tie 'body' to the 'json' parameter, and the unrelated url, host, and zone parameters remain unexplained in the description.

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 validates whether a body is valid JSON, with a specific verb and resource. It is distinct from sibling tools, none of which are JSON validators, though it does not explicitly name any sibling as an alternative.

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 guidance about when to use this tool versus alternatives, nor any exclusions or conditions. The only clue is the imperative purpose statement, which merely implies usage rather than defining context.

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