Europe/Istanbul clock

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

The description adds only "Page content is not stored," which is a useful non-retention guarantee. With no annotations, the description carries the full burden, but it does not disclose that the tool likely performs a network fetch, what error/status behavior to expect, or how the json and zone inputs behave beyond their schema descriptions. This is a significant transparency gap for a tool with four unrelated optional inputs.

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 the primary action and output front-loaded, and no filler words. The brevity is efficient, though it partly contributes to the description's incompleteness regarding the other schema fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has four optional parameters, no output schema, no annotations, and overlapping siblings (e.g., normalize-url, validate-json, timezone-clock), yet the description references only the URL behavior. The mismatch between the URL-only description and the json/zone schema fields leaves an agent unable to reliably select or invoke 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 met without needing the tool description to document each parameter. The description adds some meaning to the url parameter by mapping it to host/scheme/status output, but it adds nothing to host, json, or zone, and it does not clarify whether parameters are alternatives, combinable, or mutually exclusive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "Return host, scheme, and HTTP status for a URL." This clearly distinguishes it from siblings like normalize-url (which returns a normalized URL rather than status) and validate-json (which validates JSON). However, the input schema also exposes json and zone parameters that the description never mentions, so the overall purpose is somewhat ambiguous beyond the URL behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no exclusions, and no reference to alternatives such as normalize-url or validate-json. With 0 required parameters and four heterogeneous optional fields (url, host, json, zone), the agent cannot determine which invocation mode is appropriate or when to prefer this tool over 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?

With no annotations, the description must carry the burden of behavioral disclosure. It adds one useful trait: 'No identifiers are retained,' which clarifies data handling. However, it does not disclose whether the operation is read-only, has side effects, or how inputs are used beyond that retention note.

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 only two sentences and both are purposeful: the first states the action and the second adds a privacy behavior. It is appropriately front-loaded and has no filler, though the first sentence could be more specific.

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, but the description does not explain what the classification means, how the parameters influence it, or what the response looks like. This leaves significant gaps for an agent trying 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 schema already documents the four parameters meaningfully. The description adds no parameter-specific meaning, but per the baseline rule for high schema coverage, a 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Show how this request is classified'), so it is not a tautology, but the kind of classification and what 'this request' refers to remain vague. It does not distinguish the tool from siblings like citation 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?

There is no guidance on when to use this tool versus the sibling tools, and no context or exclusions are given. The description implies the agent can invoke it to see a classification, but that is left entirely to inference.

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 behavioral disclosure burden. It does reveal the main operation and an important negative guarantee: no WHOIS or ownership data is included. However, it does not explain how the four unrelated parameters are handled, what happens when multiple are provided, or what the output structure 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 sentence with no filler or repetition. The core action and the key exclusion are front-loaded. Some might argue it is too terse given the four-parameter schema, but as a concise description it is well structured.

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, this description is incomplete. It only explains the hostname-labeling behavior and ignores the url, json, and zone inputs entirely. An agent would be uncertain what output to expect or when to supply the non-host 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. The description adds no parameter-specific meaning beyond the schema; it only implies that 'host' is the relevant input for splitting into labels. The url, json, and zone parameters remain unexplained at the description level, but the schema already documents each one 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 clarifies a scope boundary by saying 'without WHOIS or ownership data,' which helps distinguish it from data-enrichment tools. However, it does not mention the url, json, or zone parameters, so the stated purpose is narrower than the full input 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?

The description gives no explicit guidance on when to use this tool versus alternatives. The phrase 'without WHOIS or ownership data' implies it should not be used when such data is needed, but it names no alternative tool or concrete condition. Given the sibling tools like normalize-url and validate-json, this lack of routing guidance is a clear gap.

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 disclosure burden, and it discloses nothing: no side effects, no return format, no operation type (read-only vs. mutation). An agent cannot predict whether calling this tool produces a list, validates input, or discards data beyond the 'discarded after the check' note in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief but inadequate — it is a sentence fragment, not a specification. The brevity reflects under-specification rather than efficient front-loading, since the single phrase fails to state the tool's purpose or action.

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 4 parameters, no annotations, and no output schema, the description is far too thin to support correct tool selection or invocation. The unknown return behavior and the unexplained url/host/json params leave critical gaps that no structured field fills.

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 baseline is 3, but the description adds zero connection between the 'IANA timezone names' concept and the url/host/json parameters. Only 'zone' aligns with the tool name; the others appear unrelated, creating a semantic mismatch that could mislead parameter selection.

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, 'Common IANA timezone names for clock calls,' is a noun phrase with no verb — it restates the tool name 'iana-zones' without stating what action the tool performs. It never says whether the tool lists names, validates a zone, or returns data, and it is completely disconnected from the schema's url/host/json 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?

No guidance is given for when to use this tool versus alternatives like citation. The only hint, 'for clock calls,' is too vague to act on, and the mismatched parameters leave an agent unable to determine appropriate inputs or invocation context.

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

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

With no annotations, the description bears the full transparency burden. It does disclose that the tool performs a network fetch and returns only group counts, but it does not explain timeout behavior, error handling, redirects, or whether 'host' is used to construct the robots.txt URL. Basic transparency, but not comprehensive.

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 wasted words. The core action and output limitation are front-loaded, making it immediately scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should fully specify how to call the tool. It does not explain how the four seemingly unrelated parameters relate to fetching robots.txt, what 'group counts' means, or what happens when robots.txt is missing or invalid. The description is too sparse 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?

Schema coverage is 100%, giving a baseline of 3, but the description adds no parameter mapping. The schema descriptions for 'url', 'json', and 'zone' align with sibling tools (normalize/cite, validate JSON, timezone) rather than with fetching robots.txt, leaving the agent unable to determine which parameter supplies the target. This mismatch warrants a below-baseline score.

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 ('Fetch'), a clear resource ('public robots.txt'), and an explicit output restriction ('return group counts only'). This distinguishes it from unrelated siblings like normalize-url or validate-json despite the tool's generic input 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 provided on when to use this tool versus alternatives, no prerequisites are mentioned, and there are no exclusions or mentions of when not to use it. The 'group counts only' caveat hints at a limited use case but is not enough to route an agent.

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 add one useful behavior (query and fragment are dropped), but it is silent on the JSON 'discarded after the check' behavior, on the output shape, on error handling, and on the fact that behavior changes depending on which parameter is passed.

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 crisp sentences with no wasted words and the primary behavior is front-loaded. However, the brevity is achieved partly by omitting the tool's other modes, so it is efficient but incomplete.

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 four-parameter, zero-required tool with no annotations and no output schema, the description provides no return shape, no guidance on which input to supply, and no coverage of the JSON or timezone modes. An agent cannot reliably know the tool's full capability from this definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the schema's own parameter descriptions are already informative (e.g., 'JSON text to validate; discarded after the check'). The description adds URL-specific semantics like origin/host/path and dropping query/fragment, but says nothing about the json, zone, or host validation behavior, so it only marginally supplements 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 names a specific verb and resource — return origin, host, and path for a URL — and even discloses a behavioral constraint (query and fragment are dropped). However, the input schema exposes three other parameter families (host, json, zone) that the description never mentions, so the stated purpose is materially incomplete relative to the tool's actual scope.

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, and no explanation of which of the four mutually-exclusive inputs should be supplied. The sibling list provides no real contrast, and the description does not warn that supplying json or zone triggers different behavior than supplying url.

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 and no output schema, the description carries the full burden of explaining behavior, but it only states what the catalog contains, not what the tool does with the supplied parameters. It does not mention whether the tool reads, checks, transforms, returns data, or has side effects; the schema hints at validation and normalization but this is never disclosed.

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 and grammatically simple, which is efficient. It front-loads the core noun phrase, though it wastes a little space on the word 'short' and does not use the brevity to clarify the tool's purpose or parameter relationships.

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 heterogeneous parameters, no annotations, and no output schema, a one-line noun phrase is severely inadequate. An agent cannot determine what inputs mean, what outputs to expect, or how this relates to HTTP status codes, making the description effectively non-actionable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides 100% coverage with individual descriptions for each parameter, so the baseline is 3. However, the tool description itself adds no parameter-level meaning, and the gap between 'HTTP status codes' and parameters like 'zone' or 'json' is unexplained, slightly undermining the schema's clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially a noun phrase restating the tool name: 'status-catalog' becomes 'catalog of common HTTP status codes'. It lacks a specific action or verb, and the input schema (url, host, json, zone) has no obvious relationship to a catalog of HTTP status codes, making it harder for an agent to infer what invoking this tool actually does.

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 the sibling tools 'citation' and 'compatibility'. The description provides no context about typical use cases, prerequisites, or conditions under which this tool should be preferred, 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 burden of behavioral disclosure. It conveys a read-only lookup but does not mention how invalid zones are handled, whether url/host/json are ignored, or any network/response behavior. The mismatch between the description and the schema's unrelated parameters compounds this gap.

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 conveys the core function with no filler. This is appropriately concise, even if it sacrifices completeness elsewhere.

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 parameters and no output schema or annotations, yet the description explains only the zone-based time lookup. It does not clarify the role of the other three schema properties or describe the return value, leaving an agent under-informed for 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 parameters are already documented in the schema. The description adds no meaningful parameter detail beyond implying that zone is the relevant input; it leaves url, host, and json disconnected from the stated purpose.

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 and resource: returning the current time for a named IANA timezone. It is clear and distinguishable in intent, though it does not explicitly differentiate itself from a similar sibling such as 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?

No guidance is given about when to use this tool versus alternatives, and no exclusions or conditions are stated. The sole sentence describes what it does, not when it should be chosen.

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 states the output is the current local time, but does not explain how the unrelated parameters (url, host, json) are handled, whether the zone parameter can override the fixed Europe/Istanbul zone, or whether any network/read behavior is involved.

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 redundant wording. It efficiently communicates the core purpose and earns its place without 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?

The tool has no output schema, no annotations, and four optional parameters, three of which appear unrelated to the stated purpose. The description does not clarify which parameters to pass, whether the zone parameter is required, or how the other parameters are treated, leaving an agent with insufficient guidance for 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 does not add parameter-level guidance, and it actually creates some confusion by naming a fixed timezone while the schema includes a generic 'zone' parameter. Still, the schema itself documents all parameters 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 states the tool returns the current local time for Europe/Istanbul, which is a specific resource. It distinguishes from siblings like utc-time and timezone by naming the exact zone, though it lacks an explicit verb like 'returns' and the presence of a generic zone parameter creates slight ambiguity.

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 by the description: use this tool when you need the current local time in Europe/Istanbul. However, it does not explicitly mention alternatives such as utc-time or the generic timezone tool, nor does it state when this tool should be preferred or avoided.

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, yet it discloses nothing beyond the phrase 'Current UTC timestamp.' It does not explain that url, host, json, and zone are ignored, nor does it state the output format or time source. This is a serious disclosure gap.

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 and front-loaded, satisfying conciseness. However, it is under-specified rather than efficiently complete; a sentence clarifying parameter irrelevance would improve it without bloat.

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 parameters, no annotations, and no output schema, this description is inadequate for correct invocation. The core ambiguity of which parameters, if any, should be passed remains 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 100%, which normally earns a 3 baseline, but the four parameters (url, host, json, zone) appear unrelated to retrieving a UTC timestamp. The description adds no clarification about whether these parameters are accepted, ignored, or conditionally used.

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' essentially restates the tool name 'utc-time'. It conveys the resource (UTC time) but lacks a verb, scope, or any differentiation from siblings like citation or 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?

There is no guidance on when to use this tool versus the sibling tools, nor any indication that all four parameters are optional and likely irrelevant. An agent gets no decision context.

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

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully states that the body is discarded after the check, which clarifies side effects, but it does not disclose the return format, error behavior, or whether unrelated parameters are ignored.

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 appropriately concise: two short sentences with no filler. The second sentence adds meaningful behavioral information, though the parameter mapping is left implicit.

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 parameters, no output schema, and no annotations, this description is under-specified. It does not identify which parameter is the 'body', does not describe what the tool returns, and leaves the unrelated-looking url/host/zone parameters unexplained, increasing the risk of incorrect 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 each parameter is already documented. The description adds no additional parameter meaning and does not clarify why url, host, or zone are present for a JSON validation tool, but the schema handles the basics.

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 ('Check whether a body is valid JSON') and a clear resource. It is distinguishable from sibling tools by being the only validation-focused tool, though 'body' is slightly ambiguous without explicitly naming the 'json' parameter.

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, and no exclusions or prerequisites are mentioned. The sibling tools are unrelated, so the description does not help route an agent to this tool at the right moment.

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