IPv4 or IPv6, address discarded

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

No annotations are provided, so the description carries the full burden. It discloses the exact return fields (host, scheme, HTTP status) and a meaningful behavioral trait (content is not stored). It does not mention fetch behavior, errors, or rate limits, but for a read-only citation utility this is substantially 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 sentences, zero filler, and the most important information (return value and scope) is 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?

The description is complete for the URL-citation path but not for the tool as a whole: it gives no hint that 'json' and 'zone' are separate, supported functions. Since there is no output schema, the described return values help, but the multi-purpose nature of the tool is hidden.

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 meaning for the 'json' or 'zone' parameters — it only covers the URL path — but the schema already documents those parameters with adequate one-line descriptions.

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 ('Return') and resource ('host, scheme, and HTTP status for a URL'), and adds a clarifying disclaimer ('Page content is not stored'). It is clear on the core behavior, but it does not differentiate from the sibling tools 'url-normalize' and 'host', which overlap with the same domain.

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 implied: use this when you need citation-style metadata for a URL. The 'Page content is not stored' note gives some decision guidance, but there are no explicit when-to-use/when-not-to-use statements or references to alternative 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 provided, the description carries the full burden of behavioral disclosure. It does disclose 'No identifiers are retained,' which is useful privacy context, but it does not say whether the tool is read-only, what side effects occur, or what the response contains.

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 filler. The main purpose is front-loaded, and the privacy note is a meaningful 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?

For a tool with no annotations, no output schema, and four optional parameters, the description is too thin. It does not explain what kind of result is returned, how the parameters are interpreted, or why an agent would invoke this tool over a sibling.

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 all four parameters (url, host, json, zone) are already documented in the schema. The description adds no additional meaning about how these parameters influence the classification.

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') and a clear resource ('this request'). However, it does not define what 'classified' means or how this differs from siblings like 'citation' and 'domain-shape'.

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. It neither states conditions for use nor mentions sibling tools as exclusions.

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 fully disclose behavior, but it only states that the tool does not include WHOIS/ownership data. It does not mention any side effects, read-only guarantees, or the fact that json input is 'validated and discarded' per the schema, leaving mutation and data-retention behavior unspecified.

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 concise sentence and is easy to parse. However, it is under-specified for a tool with four unrelated parameters; brevity here sacrifices completeness rather than being efficient.

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, no annotations, and four optional parameters. The description leaves unclear what the result of splitting looks like, how url vs host are chosen, why json and zone exist, and what happens after the operation. For an agent to call this correctly, significant inference is required.

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 'hostname', and it fails to connect url, json, or zone to the stated operation, but the schema already documents each parameter's format, so the description does not need to compensate.

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 ('split a hostname into labels') and an explicit exclusion ('without WHOIS or ownership data'). However, the input schema includes url, json, and zone parameters whose descriptions point to URL normalization/citation, JSON validation, and timezone handling, none of which are accounted for by the description, leaving the tool's actual scope 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?

No explicit when-to-use or alternative tool guidance is provided. The only implied signal is the exclusion of WHOIS/ownership data, which suggests a use case but does not tell an agent when to prefer this tool over siblings or what inputs are 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?

No annotations are provided, so the description carries the full burden of disclosing behavior, but it discloses virtually none. It does not state what happens when invoked, what the output is, whether it is read-only, or how url, host, and json are involved. Even the implied read-only nature of a name catalog is not explicit.

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 contains no fluff, but it is under-specified to the point of being a fragment. It reads more like a title than a tool definition, so the brevity is not appropriately sized for the complexity of 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 4 loosely related optional parameters, no output schema, no annotations, and a vague one-line description, there is not enough information for an agent to know what to pass, what to expect back, or when to use the tool. The description is not complete enough for reliable selection or 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 real parameter meaning beyond the schema; it only echoes the zone parameter concept. It does not clarify why url, host, and json are accepted parameters for a tool about IANA timezone names.

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 a noun phrase, not a clear verb+resource statement. 'Common IANA timezone names for clock calls' essentially restates the tool name and adds only 'common' and 'for clock calls,' without saying whether the tool lists, validates, returns, or filters timezone names. It also fails to distinguish itself from siblings like lookup-timezone or clock.

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. The phrase 'for clock calls' provides a weak contextual hint, but there are no exclusions, conditions, or named sibling alternatives. An agent cannot determine when this tool is the right choice.

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 behavioral disclosure. It discloses that only group counts are returned ('return group counts only'), which is useful, but it does not disclose side effects (none expected for a fetch), network behavior, response format, throttling, or error handling (e.g., what happens for non-robots.txt URLs or invalid hosts).

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 zero waste. It front-loads the primary action and scope clearly. It earns a high score for conciseness, though it is so brief that it lacks important 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?

Given the tool is a fetch operation with no annotations and no output schema, the description is too incomplete. It does not clarify which parameter is the target (url vs host), why 'json' and 'zone' parameters exist, what the return structure looks like, or error behavior. The 4-parameter schema with 100% coverage still leaves semantic gaps that the description should fill.

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 the schema documents all four parameters. However, the description adds almost no meaning beyond the schema. It does not map parameters to behavior (e.g., whether 'url' is the target to fetch, whether 'host' is an alternative to 'url', or what 'json' and 'zone' have to do with robots.txt). The mismatch between the description (robots.txt only) and schema (url, host, json, zone) creates confusion.

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 ('Fetch') and resource ('public robots.txt'), and an action ('return group counts only'). However, it does not differentiate itself from sibling tools beyond being specific about the robots.txt resource, and the schema parameters (url, host, json, zone) suggest broader functionality that is not reflected in the description.

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. It implies usage via the verb 'Fetch', but does not specify conditions, prerequisites (e.g., URL must be publicly accessible), or 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, the description must carry the behavioral disclosure burden, but it only says 'address discarded.' It does not explain what is returned, whether there are side effects, what errors occur, or why the address is discarded. This is too thin for a tool with unknown 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 but not efficiently informative. 'IPv4 or IPv6' largely repeats the tool name, and the missing verb makes it an under-specified fragment rather than a well-structured tool description.

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 annotations, no output schema, four optional parameters, and a highly terse description, the tool is not adequately specified for an agent to confidently select and invoke it. The one useful behavior hint ('address discarded') is not enough to cover the missing input, output, and usage context.

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. However, the description does not link its mention of 'address' to any specific parameter, and it does not clarify whether url, host, or something else should be supplied for the IP-version check. The schema descriptions are helpful, but the tool description adds no additional parameter 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 is a fragment: 'IPv4 or IPv6, address discarded' offers no verb and no explicit resource, so it does not state what the tool actually does. It restates the tool name's concept without clarifying whether the tool returns a version, validates an address, or filters something.

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 rather than a sibling such as normalize-url, validate-json, or domain-shape. It also does not mention which input type (url, host, json, or zone) is appropriate, leaving the agent to guess.

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?

There are no annotations, so the description carries the full burden of behavioral disclosure. It does disclose that query and fragment are dropped, but it omits any behavior around JSON validation or timezone handling, and provides no information about return format, errors, or side effects. The schema note that JSON is 'discarded after the check' is not reflected in the description.

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, efficient sentence that front-loads the core behavior and states the drop behavior afterward. It is concise and well-ordered, though it omits important context about other parameters.

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, and four parameters, but the description only covers URL-related behavior. It does not explain how to use `json` and `zone`, what the output looks like, or how `host` relates to the return value. This leaves the description incomplete for an agent to call the 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?

Schema description coverage is 100%, so the baseline is 3, but the description adds no parameter-specific meaning and fails to connect `json` and `zone` to the described URL behavior. The `host` parameter role is also ambiguous relative to the stated output. This disconnect pulls the score down.

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 a specific verb and resource: 'Return origin, host, and path for a URL.' However, the input schema includes `json` and `zone` parameters that are not mentioned in the description, making the tool's full purpose ambiguous and potentially misleading about what it actually handles.

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, nor any exclusion criteria. It only implies that it is for extracting URL components, but the unrelated `json` and `zone` parameters add confusion about when this tool 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, the description carries the full burden, but 'Short catalog' only hints that this is a static reference. It does not disclose what the parameters do, whether any inputs affect the catalog, or what the agent can expect as a 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 minimal and front-loaded with the subject matter, but it is under-specified rather than efficiently complete. A single noun phrase does not give the agent enough structure to act on.

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 4 optional parameters, no output schema, and unclear parameters relative to its stated purpose, the description is fundamentally inadequate. An agent cannot determine what inputs to supply or what the tool returns.

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?

Although schema coverage is 100%, the parameter descriptions (URL to normalize, hostname, JSON to validate, timezone zone) appear copied from sibling tools and are semantically unrelated to an HTTP status code catalog. The description adds no clarification, so the baseline of 3 is not earned.

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 the resource (catalog of common HTTP status codes) and is clearly distinct from siblings like validate-json or timezone. However, it uses no operation verb — 'catalog' as a noun does not say whether the tool lists, looks up, or explains status codes, leaving the agent to infer the action.

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, nor how to invoke it. An agent gets no context about whether to pass a code, search for one, or request the full list.

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 behavioral disclosure, and it only says the output is the current time. It does not mention output format, what happens for invalid IANA names, error behavior, or that only the 'zone' parameter is relevant while three other schema parameters are unrelated 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 a single short sentence, which is front-loaded and easy to read, but it is under-specified rather than efficiently concise. Given the misleading schema parameters, a slightly longer description that explicitly pointed to 'zone' would have added necessary value.

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?

Context vast — the tool has four optional parameters, no output schema, and no annotations, and the description leaves the invocation contract underspecified. It does not say which parameter to provide, what response shape to expect, or why the url/host/json parameters exist; the description-schema mismatch is left completely unresolved.

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 formally 100%, but three of the four parameters (url, host, json) describe normalization, citation, and validation concerns that are irrelevant to the timezone purpose. The description names no parameters, so it fails to disambiguate the useful 'zone' parameter from the distractors—leaving the agent to infer the intended parameter on its own.

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 time in a named IANA timezone,' identifies a specific resource (named IANA timezone) and an output (current time), which clearly distinguishes it from siblings like fetch, scrape, and validate. However, it is phrased as a noun fragment with no explicit verb, and the schema's url/host/json parameters undermine the clarity by suggesting unrelated capabilities.

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 offers no guidance on when to use this tool versus siblings such as lookup, normalize, or validate. It does not state prerequisites, when not to use it, or any conditions that would make an alternative preferable, leaving the agent to guess.

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 'Current UTC timestamp' is essentially a tautology of the tool name. It discloses no response format, precision (seconds vs milliseconds), or side effects, and it fails to address the serious mismatch where the schema asks for URL/JSON/timezone parameters that have nothing to do with returning a UTC timestamp.

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 words is maximally terse, but this reads as under-specification rather than efficient conciseness. A tool whose schema exposes four misleading parameters needs more than a noun phrase to earn 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 definition is grossly incomplete for this tool's actual shape: no output schema, no annotations, and a four-parameter schema that appears copied from sibling tools. An agent cannot know the return format, which parameters (if any) to pass, or how this differs from the timezone sibling.

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%, which normally earns a baseline of 3, but the parameters documented (url, host, json, zone) are semantically unrelated to the tool's stated purpose. The description adds no explanation of how these parameters relate to obtaining a UTC timestamp, leaving an agent unable to determine whether they should be passed at all.

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' states a clear resource and an implied retrieval action, so an agent can tell what the tool fundamentally does. However, it does not differentiate from the sibling 'timezone' tool, and it silently ignores the fact that the schema exposes unrelated parameters (url, host, json, 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 on when to invoke utc-time versus the sibling tools (especially timezone, but also normalize-url and validate-json). The description also gives no hint about whether any of the four optional schema parameters should be supplied, which is a real decision an agent must make with zero support.

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 discloses that the body is discarded, which is valuable, but with no annotations and no output schema it fails to explain what the tool returns (e.g., a boolean, error messages, or HTTP status). This is a significant behavioral gap for an agent trying to use 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?

Two short sentences with no filler. The core purpose is front-loaded and the discarded-body behavior is communicated in a single extra clause. 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 straightforward validation tool, the description is under-specified because it omits the return format and any error-handling details. Without an output schema or annotations, an agent cannot confidently determine what success or failure looks like after invoking 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 coverage is 100%, so the parameters are already documented in the schema. The description adds no parameter-level meaning, but the baseline of 3 is appropriate because the description does not need to repeat what the schema 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 clearly states the action ('check') and resource ('whether a body is valid JSON'), which is specific and not a tautology. It also adds the useful consequence that the body is discarded. There are no similar siblings to differentiate from, so this is clear enough.

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, and no mention of when not to use it. The intended use is implied but never stated explicitly in terms of selection criteria or exclusions.

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