Port 80

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

With no annotations, the description carries the full burden, and it does add one useful behavioral disclosure: 'Page content is not stored,' which addresses a privacy concern. However, it does not disclose error behavior, HTTP method used, return format, or what happens for non-HTTP URLs.

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 privacy note earns its place. It is efficient, though it could have used the second sentence to clarify the other parameters instead.

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 covers only the URL-checking behavior while the schema exposes three additional parameters (host, json, zone) whose purpose is never connected to the described behavior. With no output schema and no annotations, an agent lacks enough context to understand the tool's full interface or its return format.

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 documents all four parameters (url, host, json, zone). The description adds context for the url parameter via the host/scheme/status outputs, but it does not explain how the host, json, or zone parameters relate to the stated purpose, leaving their role ambiguous.

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') and names concrete outputs (host, scheme, HTTP status) for a URL, making the tool's core purpose clear. It differentiates from siblings like port-status and validate-json by listing its specific output fields, though it does not explicitly name any alternative 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 statement implies when to use this tool: when an agent needs a URL's host, scheme, or HTTP status. However, it provides no explicit guidance about when not to use it or which sibling tool to prefer (e.g., normalize-url), leaving the routing decision 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds one genuinely useful behavioral fact — 'No identifiers are retained,' signaling a privacy-safe check — but it does not disclose whether the operation is read-only, what errors or failure modes exist, or whether the tool has side effects. For a tool with zero annotation coverage, this is minimal disclosure that leaves most of the burden unmet.

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 zero filler. The primary purpose is front-loaded, and the privacy note earns its place as a distinct second sentence. Nothing could be removed without losing meaning.

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 only four optional parameters, no nested objects, no enums, and full schema coverage, the structural complexity is low. However, the absence of an output schema means the description should clarify what a 'classification' result looks like, which it does not. An agent can invoke the tool but cannot predict or interpret its return value, and sibling differentiation is missing, so adequacy is borderline.

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 optional parameters are already documented with purpose and type in the schema itself. The description adds no parameter-level meaning — it never explains which parameter constitutes 'this request' or how the four inputs relate to classification. The baseline 3 applies because the schema does the heavy lifting and no compensation is needed.

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 ('Show') and a resource ('this request'), but 'classified' is never defined — an agent cannot tell what taxonomy or categories the tool returns, or how classification differs from the siblings' normalize/validate/cite behavior. It is clear enough to be a read-like inspection tool, but the ambiguity of the central concept prevents a higher score.

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

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

There is no guidance on when to call this tool versus its siblings (citation, domain-shape, normalize-url, validate-json). It also does not state whether the 'request' is identified by url, host, json, or zone, or what happens if multiple parameters are supplied. An agent must infer the intended use case entirely.

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

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

With no annotations, the description carries the full burden of explaining behavior. It discloses one useful limitation (no WHOIS/ownership data), but it does not state whether the operation is read-only, how url/json/zone inputs are handled, or what the output looks like. This leaves the agent uncertain about actual behavior beyond the simple split.

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 front-loaded, economical sentence with no filler; the core operation appears immediately. It is concise, though the brevity comes at the cost of not addressing the other three 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?

For a tool with four heterogeneous parameters, no annotations, and no output schema, a one-sentence description is insufficient. The description does not say which parameter is the primary input, whether a url is also accepted for hostname extraction, what happens to json and zone inputs, or what result the agent should expect.

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 input schema already documents all four parameters clearly. The description adds no new meaning beyond the word 'hostname', which aligns with the host parameter; it does not clarify how url, json, or zone relate to the splitting behavior.

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 ('split') and resource ('hostname into labels'), and adds a meaningful exclusion ('without WHOIS or ownership data') that separates it from domain-enrichment tools. However, it does not explain why the schema also contains url, json, and zone parameters, so the stated purpose only partially covers the tool's apparent input surface.

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 siblings like normalize-url or validate-json. The phrase 'without WHOIS or ownership data' says what the tool does not return, but it does not indicate which parameter to supply or 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, but it reveals nothing about return values, side effects, validation behavior, or how the url/host/json parameters are used. The description's narrow timezone framing even omits the JSON validation behavior implied by 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 short (seven words), but this is under-specification rather than conciseness. The single sentence does not earn its place because it fails to convey the tool's operation, parameter usage, or relationship to siblings.

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, the description is entirely inadequate. An agent cannot determine when to call it, what inputs are valid, what it returns, or how it differs from the sibling tools.

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

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

Although schema description coverage is 100%, the tool-level description adds no meaning about how the four parameters relate; it only loosely corresponds to 'zone' and completely ignores url, host, and json. The stated purpose ('timezone names') actively conflicts with three of the four parameters, leaving an agent unable to determine what to pass.

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 essentially a restatement of the tool name with a vague usage context and no verb specifying what the tool does. It also conflicts with the input schema, which includes url, host, and json parameters that have nothing to do with timezone names, making the intended purpose misleading.

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

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

No guidance is given on when to use this tool versus its siblings (citation, compatibility). The phrase 'for clock calls' offers at most a thin implied context, and nothing explains when not to use it or which of the four unrelated parameters actually applies to a given task.

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

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

With no annotations, the description carries the behavioral disclosure burden. It reveals that the tool performs a network fetch ('Fetch a public robots.txt') and that output is deliberately limited to group counts. However, it does not disclose failure behavior, handling of missing robots.txt, rate limits, or whether the operation is read-only beyond implication. This is adequate but shallow.

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, direct sentence that front-loads the verb and resource. It wastes no words and is easy to parse. The 'only' even manages to communicate intentional output restriction without extra phrasing.

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 4 optional parameters, no output schema, and no guidance on which parameters to provide for a successful robots.txt fetch. The description does not explain how to construct a call, what 'groups' refers to, or what a meaningful response looks like. An agent would struggle to select the correct parameter for the intended target.

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 are generic and mismatched with the tool's purpose: 'url' says 'HTTPS URL to normalize or cite', 'host' says 'Public hostname', and 'json' is about validation. The description does not clarify which parameter is the robots.txt source or how the others relate to the fetch. High schema coverage does not help when the schema descriptions are vacuous and unconnected to the tool's stated action.

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

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

The description states a clear, specific action: 'Fetch a public robots.txt and return group counts only.' It names the resource (robots.txt) and the exact output shape (group counts), which is enough for an agent to understand the core function and distinguish it from unrelated sibling tools.

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

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

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites (e.g., which input identifies the target host). It does not say when not to use it or mention sibling tools. The agent must infer the intended use case entirely from the one-sentence description.

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. It discloses that query and fragment are dropped, which is useful, but it doesn't mention whether a URL parameter is required, what happens for invalid URLs, or any side effects (though 'normalize' implies a transformation). The description is minimal on behavioral context.

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, front-loaded with the core purpose. No wasted words.

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 parameters but 0 required, and no output schema or annotations, the description leaves ambiguity about which parameters are actually used and what the return value looks like. It seems the tool might only use 'url' and ignore 'host', 'json', 'zone' – that confusion is not resolved.

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 'normalize or cite' for the URL parameter, slightly enhancing meaning, but provides no extra context for other parameters.

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 ('Return origin, host, and path for a URL') and the resource (URL). It is clear what the tool does. However, it doesn't contrast with sibling tools, so it's not a 5.

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

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

No guidance is given about when to use this tool vs alternatives. The description does not mention any exclusions or conditions for use.

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 does not disclose whether the tool returns a boolean, validates something, performs a network check, has side effects, or what it does with the url, host, json, and zone parameters.

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, but this is under-specification rather than effective brevity. It does not front-load useful behavioral or parameter context, and it is far too small to support a tool with four unrelated 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?

With no annotations, no output schema, and a one-sentence description, the tool is fundamentally incomplete. An agent cannot know what the tool returns, what inputs are relevant, or why this tool exists alongside the listed sibling tools.

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

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

Schema coverage is 100%, but the tool description adds no relationship between the parameters and the stated purpose. The url, host, json, and zone parameters all appear irrelevant to whether port 80 is common, and the description gives an agent no basis for deciding which optional parameters to provide.

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 that essentially restates the tool name: 'port-80' becomes 'Whether 80 is a common TCP/UDP port.' It lacks an action verb such as 'checks' or 'returns' and does not say what the tool actually does or how it differs from sibling tools.

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 or which sibling tool would be an alternative. The description only poses a yes/no question and leaves all invocation context unstated.

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 reveals nothing: no side effects, no input handling, no output behavior, no constraints. An agent cannot predict what happens when it passes a URL, host, JSON string, or timezone.

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 this is under-specification rather than conciseness. A single noun phrase with no verb, no usage context, and no parameter mapping does not earn its place as a useful tool definition.

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 parameters, no annotations, no output schema, and no usage guidance, this description is completely inadequate. The agent lacks essential information about what the tool does with each input, what it returns, and when to invoke it.

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 has a definition and the baseline is 3. However, the tool description does not explain why these four heterogeneous parameters exist together or what role each plays, so it adds no meaning beyond the schema.

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

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

The description 'Short catalog of common HTTP status codes' basically restates the tool name with more words. It identifies a resource but provides no verb or action, and it does not clarify how the four unrelated parameters (url, host, json, zone) relate to a 'catalog of status codes'.

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

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

No guidance is given on when to use this tool versus its siblings (citation, compatibility, etc.), nor when to use each parameter. The vague noun-phrase description leaves the usage conditions 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 full burden of behavioral disclosure, but it only states the core function. It does not describe the output format, whether it accepts abbreviations, what happens for invalid zone names, or any side effects (even though a read is implied).

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 7-word sentence with no filler. Every word earns its place, and the core idea is front-loaded.

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 simple time lookup the description is nearly sufficient, but the absence of any output schema or annotations, combined with the schema's unrelated parameters, leaves important gaps. An agent cannot tell what the response looks like or how to handle invalid input.

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% for all four parameters, including 'zone' with 'IANA timezone name'. However, the schema also includes url, host, and json parameters that appear unrelated to a timezone lookup, which could confuse an agent. The description adds no extra meaning beyond 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 'Current time in a named IANA timezone' uses an implied verb with a clear resource and scope. It is specific enough to differentiate from the siblings, which all concern URLs, citations, or JSON rather than 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 sibling is mentioned as an alternative or exclusion. The description only states what it does, not when it should be selected.

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?

Annotations are absent, so the description carries the full burden. It states that the tool returns the current UTC timestamp, but does not disclose whether it returns seconds, milliseconds, an ISO string, whether it has any side effects, or any rate or auth concerns. For a simple read-like tool this is a partial disclosure, but not enough to be 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?

The description is extremely concise—one short clause—but this is under-specification rather than efficient conciseness. It does front-load the core idea but leaves out essential behavioral and parameter context, so the brevity does not serve the agent.

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?

This is a four-parameter tool with no output schema and no annotations. The description explains nothing about how the parameters relate to the tool's purpose, and the sibling tools are unrelated. The description is far too thin to enable correct invocation for any likely use case.

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 lists four parameters (url, host, json, zone) with 100% schema description coverage, but the tool description makes no mention of any of them. The parameters appear entirely unrelated to a UTC timestamp function, and the description provides zero guidance on which, if any, are used or how they affect the output. This is a critical gap.

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 verb+resource but is extremely terse, and the sibling tool names (citation, compatibility, domain-shape) are unrelated, so no differentiation is offered. It does tell the agent this tool returns the current UTC time, which is minimally clear, but lacks any detail about response format or 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 guidance on when to use this tool versus alternatives. The sibling list contains unrelated tools, and the description does not mention any conditions, prerequisites, or exclusions. An agent cannot tell whether this tool is preferred for time-related operations or how it relates to the other 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 full responsibility for behavioral disclosure. It does disclose the key side effect that the body is discarded, which is valuable, but it fails to describe the return value or success/failure behavior, which an agent needs to know for a validation tool without an output 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?

Two short sentences carry the core message with zero filler. The action is front-loaded, and the side-effect note is immediately after.

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 and no output schema, the description is too sparse. It does not explain what the tool returns, how the JSON body is supplied given the unrelated parameters, or why url, host, and zone are part of the schema. An agent would be uncertain how to call it correctly.

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

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

Schema description coverage is 100%, so the baseline is 3. The description adds no new parameter-level meaning beyond the schema; the `json` param description already repeats the tool description, and the unrelated parameters url, host, and zone are not reconciled with the tool's 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 clearly states a specific verb and resource: 'Check whether a body is valid JSON.' This directly identifies the tool's function and, given sibling tools are all URL/time/domain related, it is easy to distinguish from alternatives.

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 when to use the tool (to validate JSON) and the note 'The body is discarded' provides an explicit exclusion: do not use this tool if you need the body later. It does not name alternative tools, but none of the siblings compete with this function.

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