UTC weekday name

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 a notable behavioral trait — 'Page content is not stored' — and states the HTTP status check. However, it does not explain that this tool performs a network request, any potential latency/errors, or the meaning of the returned values beyond their names. Partial transparency, no contradiction.

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: 'Return host, scheme, and HTTP status for a URL. Page content is not stored.' The core purpose is front-loaded, and the behavioral caveat follows immediately. 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?

Despite having exactly four parameters and no output schema, the description only explains the URL-related behavior. It does not clarify why 'json' and 'zone' parameters exist, what output format is returned, or how the tool handles errors or redirects. For a tool with this parameter mismatch, the description leaves significant 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?

Schema description coverage is 100%, so the baseline is 3. Each parameter has a brief schema-level description, and 'url' is echoed in the tool description as 'HTTPS URL to normalize or cite.' However, the description adds no semantic linkage for the seemingly unrelated parameters 'host,' 'json,' and 'zone,' which do not clearly fit the 'citation' purpose stated 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 states a specific verb and resource: 'Return host, scheme, and HTTP status for a URL.' This clearly indicates the tool performs a URL inspection/HTTP check. It does not explicitly differentiate from sibling tools, though it attempts to with the 'Page content is not stored' caveat.

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 about when to use this tool versus alternatives, nor are there exclusions or conditions. The sibling-tools list appears garbled/corrupted, so no alternative routing is provided. The only implicit context is that the tool is for URL citation checks, which is weak.

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?

The description adds meaningful behavioral context with 'No identifiers are retained', implying a stateless privacy guarantee, and 'Show how' indicates an analysis or display operation rather than a mutation. However, it does not disclose whether the tool performs any external lookup, whether results are deterministic, or whether it only returns a categorization without processing the request. With no annotations provided, the description carries the full burden and only partially meets it.

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 short sentences with no wasted words. The primary action is front-loaded in the first sentence, and the second sentence adds a distinct privacy guarantee. This is appropriately concise and well structured for an agent to parse quickly.

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 that there are no annotations, no output schema, and four optional parameters, the description is somewhat thin. It explains the purpose and a privacy trait but does not say what the returned classification looks like, what 'classification' means in practice, or how the agent should decide between this tool and its siblings. The schema fills in parameter details, but the overall behavior remains under-specified for a complex decision.

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?

All four parameters are described in the input schema with 100% coverage, so the schema already carries the parameter documentation. The description adds no parameter-specific meaning beyond a general reference to 'this request', which does not clarify how url, host, json, or zone map to the classification behavior. A baseline of 3 is appropriate because the schema covers the parameter semantics 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 action, 'Show how this request is classified', which distinguishes it from the sibling tools that likely perform normalization, validation, or citation. However, 'classified' is a bit vague—it does not specify what categories or dimensions the classification produces. Overall it is clear enough for an agent to understand the core function.

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 siblings like normalize, validate, or citation. It does not state what input types are appropriate or what 'this request' refers to in terms of the available parameters. The agent must infer usage from the schema and tool name alone.

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 present, the description must carry the behavioral disclosure burden, but it only states the core split operation and one negative guarantee. It does not disclose how a URL vs hostname is treated, what the output structure is, whether any network access occurs, or how invalid or empty input is handled, so an agent cannot predict runtime 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?

A single front-loaded sentence states the operation first and then the exclusion; every word earns its place. There is no redundancy or 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 tool with no output schema and no annotations, the description is too thin: it omits the result format, the expected input parameter, and error semantics. An agent would not be able to confidently construct a correct call or interpret the response from this definition alone.

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?

Input-schema coverage is 100%, so the baseline is 3: each parameter has a description. The tool description adds no parameter-specific guidance, and because all four parameters are optional, it is not obvious whether to pass host, url, or ignore json/zone; the description's 'hostname' maps most naturally to the host 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 uses a specific verb and resource ('Split a hostname into labels') and immediately scopes the tool with 'without WHOIS or ownership data,' making its intent unmistakable. This also distinguishes it from siblings like normalize-url, which normalizes rather than splits, and from any ownership-lookup tool.

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 purpose implies the usage context: use this when you need hostname labels, not WHOIS or ownership data. However, it never explicitly names alternatives or states when this tool should be preferred over siblings such as normalize-url or citation, so the guidance is mostly implied rather than direct.

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 full behavioral burden. It discloses no behavior: no indication of side effects, return value, whether it lists data or performs a lookup, or any constraints. The bare noun phrase provides essentially no behavioral information.

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, but it is under-specified rather than concise. A single noun phrase does not earn its place because it fails to communicate the tool's action, inputs, or output.

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 and no output schema, yet the description explains neither return values nor how it relates to the four provided parameters. The name suggests a list of timezone names, but an agent has no reliable basis for calling or interpreting the tool.

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 a baseline of 3 applies. The description adds no parameter-level meaning beyond the schema and leaves unclear why url, host, and json are present for a tool about IANA timezone names, but the schema itself already documents each property.

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 identifies a resource ('Common IANA timezone names') rather than an operation. It does not state what the tool actually does, such as returning or validating timezone names, making it little more than a restatement of the tool name with a vague 'clock calls' context.

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: an agent might use this tool when needing timezone names for clock-related tools. However, it gives no explicit guidance on when to choose this over siblings like 'timezone' or 'utc-time', nor any exclusions or 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 disclosure burden. It does reveal an external read ('Fetch') and a restricted output ('group counts only'), but it leaves unspecified behavior around missing or inaccessible robots.txt files, redirects, and what exactly constitutes a group count.

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 short sentence with no filler; the core resource and output constraint are front-loaded. 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?

For a tool with four optional parameters, no output schema, and no annotations, a single sentence is insufficient. Missing parameter mapping, expected response format, and edge-case behavior make the definition incomplete for reliable 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?

Even though all four parameters have schema descriptions, those descriptions reference normalization, citation, JSON validation, and timezones, which do not clearly map to 'robots.txt'. The tool description does not say which parameter identifies the target site, so an agent cannot confidently populate 'url' vs 'host'.

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 clear action ('Fetch'), a specific resource ('a public robots.txt'), and the exact output ('return group counts only'). This is unambiguous and sufficiently distinguishes the tool from the sibling list, none of which concern robots.txt.

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 intended use is implied by the description: use it when you need group counts from a public robots.txt. However, there is no explicit guidance about when not to use it, no alternatives named, and no context such as prerequisites or limitations.

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 behavioral disclosure burden. It clearly explains the output composition and explicitly discloses that query and fragment are dropped. It does not cover invalid-URL handling or the effect of the extra optional parameters, but the core behavior is transparent.

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 core behavior is front-loaded, and the dropped-component detail is stated efficiently. Every sentence contributes.

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 description explains return values and dropped components, but it is incomplete relative to the schema: four optional parameters exist, none are required, and the description only addresses URL behavior. An agent cannot determine whether passing json, zone, or host is valid, what happens with no arguments, or the exact output structure.

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 applies. The description adds no new meaning for host, json, or zone, and while it clarifies what happens to the url input (query/fragment dropped), that is an operational detail rather than parameter-level semantics. It does not explain which parameter to supply or whether multiple parameters are allowed.

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 ('Return'), names the resource ('a URL'), and lists exact output components: origin, host, and path. It also states that query and fragment are dropped, which clearly distinguishes it from URL-related siblings like citation or inspect-robots and from unrelated tools like timezone or validate-json.

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 the tool is for URL normalization when origin/host/path are needed, but it does not explicitly state when to use it versus alternatives. It provides no exclusion criteria, prerequisites, or pointers to sibling 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 of behavioral disclosure, but it only names a catalog of status codes. It does not state whether the tool performs a lookup, validates inputs, mutates anything, or returns data, nor does it mention side effects, permissions, or output 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?

The description is short and free of filler, but it is under-specified rather than appropriately concise. A single noun phrase is too little information for a 4-parameter tool with no annotation or output schema.

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 is no output schema and no annotations, so the description must explain what the tool returns and how the parameters relate to HTTP status codes. It fails to do either, making it inadequate for an agent to invoke 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 schema already documents each parameter. The description adds no meaning about url, host, json, or zone, and the connection between these parameters and a 'catalog of HTTP status codes' is unexplained. Baseline 3 applies because the schema covers parameter semantics.

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 'Short catalog of common HTTP status codes' essentially restates the tool name and identifies a resource, but gives no verb or action. It does not distinguish this tool from siblings like 'compatibility' or 'validate-json', leaving the actual operation unclear.

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 versus alternatives. No context, prerequisites, or exclusion criteria are provided; the agent must infer from the name alone that it is a reference lookup.

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 full burden of explaining behavior. It clearly conveys a read-only time lookup, but it does not mention anything about output format, invalid timezone handling, or the fact that url, host, and json appear irrelevant to the stated purpose.

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 eight words, front-loaded, and contains no filler. Every word contributes to the core meaning, making it appropriately concise for a simple lookup tool.

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 description is adequate for a basic call, but it is incomplete given the schema's four optional parameters and no output schema. An agent receives no guidance about the output format or whether the non-zone parameters are ignored, leaving room for misinterpretation.

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 description is not expected to restate parameter meanings. It adds no new semantic value beyond the schema, and it does not clarify that only zone is likely relevant among the four optional properties, which would have been useful.

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 the tool's function precisely: it returns the current time for a named IANA timezone. This distinguishes it from siblings like utc-time, iana-zones, and weekday-utc, and it is not a mere tautology of the tool name.

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 the tool should be used when the agent needs current local time for a named IANA timezone, and sibling names hint at alternatives for UTC or zone listing. However, it does not explicitly state when to avoid this tool or name an alternative.

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 full burden of behavioral disclosure. It merely states 'Current UTC timestamp,' which implies a read-only retrieval, but it does not disclose whether the parameters are used, ignored, or required, nor what side effects or response format to expect.

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, which is concise, but it is under-specified rather than effectively structured. For a tool with four parameters and no annotations, this brevity leaves out critical information and does not earn its place as an adequate explanation.

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 four optional parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain how the parameters should be used, what the tool returns, whether any parameters are mutually exclusive, or how it relates to sibling tools. An agent would struggle to invoke this tool 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?

The input schema covers all four parameters with descriptions (100% coverage), so the baseline is 3. However, the description adds no additional meaning about how these parameters relate to the UTC timestamp operation, and the parameter descriptions seem disconnected from the tool's stated purpose (e.g., 'JSON text to validate' and 'HTTPS URL to normalize or cite').

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 'Current UTC timestamp.' clearly names the output resource, but it lacks a verb and does not differentiate the tool from siblings like timezone or weekday-utc. It also ignores the four input parameters (url, host, json, zone) that appear unrelated to the stated purpose, leaving purpose somewhat ambiguous.

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 about when to use this tool versus alternatives such as timezone, normalize-url, or validate-json. An agent receives no context for selection or exclusion, and no mention of where this tool fits among its siblings.

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 behavioral disclosure burden. It explicitly states that the body is discarded, which is useful, but it does not describe return values, error behavior, or whether the other schema properties are used. This is helpful but incomplete.

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 short sentences with no wasted words. The purpose is front-loaded, and the disposal behavior is an important, concise addition.

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 four parameters, no required fields, no output schema, and no annotations, the description is underspecified. It does not state what the tool returns for valid or invalid JSON, which parameters are actually required for the check, or how to interpret errors. An agent would likely need to probe the tool to use it confidently.

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 on top of the schema, and the schema does document each property. However, url, host, and zone appear unrelated to JSON validation, and the description does nothing to disambiguate their role.

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: 'Check whether a body is valid JSON,' and adds the non-obvious detail that the body is discarded. It is more informative than a tautology, though it does not name sibling tools or explain why the schema also includes url, host, and zone.

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 about when to use validate-json versus sibling tools, no exclusions, and no mention of prerequisites or typical use cases. The only implicit hint is the tool name itself.

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 must carry the full burden of behavioral disclosure. It says only 'UTC weekday name' and does not state whether the tool performs a read-only lookup, returns a string, depends on the current date, or how the provided parameters affect the result.

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 short, but this is under-specification rather than effective conciseness. Three words carry almost no actionable information and provide no structure for an agent deciding whether or how to call the tool.

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 annotations, no output schema, and no usable guidance, this description is far from complete. An agent cannot determine required inputs, output format, or behavior, especially given the four unrelated-looking parameters.

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 even with no parameter details in the description. However, the description adds no meaning about how url, host, json, or zone relate to a UTC weekday, so it earns no credit beyond the schema baseline.

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 'UTC weekday name' merely rephrases the tool name and uses a noun phrase rather than a verb, so it does not clearly state that the tool returns the current weekday name in UTC. It is slightly more informative than a pure tautology because it adds the UTC scope, but it still leaves the agent to infer the operation.

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 about when to use this tool instead of siblings such as utc-time or timezone. The description provides no context, exclusions, or alternatives.

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