HTTP 410 gone

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

There are no annotations, so the description carries the behavioral burden. It adds one meaningful behavioral detail—page content is not stored—and implies an outbound network fetch by mentioning HTTP status. However, it does not disclose redirect behavior, authentication needs, failure modes, or whether any side effects occur.

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, front-loaded sentences with no filler: the first states the core function and the second adds the key privacy caveat. Every sentence 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?

With four optional parameters, no annotations, no output schema, and ten sibling tools, the description only covers the URL path and leaves host, json, and zone unexplained. An agent cannot confidently determine when to supply those fields or what the complete response shape will be.

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 meaning beyond the schema for the url parameter and completely ignores the host, json, and zone parameters, so its contribution to parameter understanding is minimal.

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's core behavior: returning host, scheme, and HTTP status for a URL, with a useful non-storage note. It does not explicitly distinguish itself from related siblings like normalize-url or status-catalog, so it stops short of full sibling differentiation.

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 or when-not-to-use guidance is provided, and no alternatives are named despite ten sibling tools such as validate-json, timezone, and status-catalog. The non-storage note weakly implies a privacy-conscious use case, but this is not enough to guide tool selection.

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 burden. It does contribute a meaningful behavioral fact: 'No identifiers are retained.' It also implies a read-only operation via 'Show', which is useful. However, it does not clarify whether the input is processed, discarded, logged, or what side effects might occur beyond identifier retention.

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 and front-loaded with the primary action, followed by a useful privacy caveat. No filler is present, though the terseness contributes to under-specification in other dimensions.

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

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

The tool has four optional parameters, no output schema, and no annotations, so the description needs to carry substantial contextual weight. It does not explain what 'classification' means, what the result looks like, or how the parameters affect the call, leaving an agent without enough context to invoke it confidently.

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

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

Schema description coverage is 100%, and each parameter has its own description, so the schema already documents individual parameters. The tool description adds no further parameter-level meaning, such as how url, host, json, and zone relate to the classification outcome.

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 an action ('Show how this request is classified') but never defines what 'request', 'classified', or 'compatibility' mean, or what classification categories are returned. It is not a tautology, but it is too vague to give an agent a concrete model of the operation.

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

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

No guidance is given about when to use this tool versus any sibling, or what kind of input should be passed when. The phrase 'No identifiers are retained' hints at a privacy-oriented use case, but it does not specify conditions for selection or 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, the description carries the full burden. It does say 'without WHOIS or ownership data', implying a local, side-effect-free operation, but it does not describe output format, error behavior, or edge cases. For a simple parser this is minimally adequate, 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 a single concise sentence that is front-loaded with the core action. It omits necessary contextual detail but does not waste words, so it earns a solid score for conciseness despite being under-specified.

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 too thin. It does not say what the output looks like, which 'labels' means, or that parameters like 'json' and 'zone' are irrelevant to the core function. An agent cannot reliably invoke this tool correctly from the description alone.

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

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

Schemas cover 100% of parameter descriptions, but the tool description ('split hostname') does not align with the actual parameters (url, host, json, zone). It never explains which parameter to use for the hostname, and 'json' and 'zone' seem unrelated to hostname splitting. The description adds more confusion than semantic value.

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 ('split a hostname into labels') and a resource ('hostname'), and clarifies that it excludes WHOIS or ownership data. This distinguishes it from tools that might enrich domains with registry data, though it doesn't explicitly contrast with siblings.

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 indication of when to use this tool versus sibling tools like 'normalize-url' or 'inspect-robots'. There are no conditions, exclusions, or alternatives mentioned, so an agent must infer usage solely from the action phrase.

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, and the description provides no behavioral detail: it does not state whether the tool makes a network call, returns a text explanation, emits an HTTP status, or has side effects. The only behavioral hint, 'discarded after the check' for the json parameter, lives in the schema rather than 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 extremely short, but this is under-specification rather than effective conciseness. It conveys a topic but omits essential operative information, so the single sentence does not adequately carry the tool's 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?

With no output schema, no annotations, and four optional parameters whose connection to 'HTTP 410' is unexplained, the definition is not complete enough for an agent to know what to pass or what response to expect. This is inadequate for a seemingly multi-purpose tool.

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

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

Schema description coverage is 100%, so the baseline is 3 even though the description adds no parameter-level meaning. The individual parameter descriptions are clear on their own, but the tool description gives no hint about why 'url', 'host', 'json', and 'zone' would be relevant to the meaning of HTTP 410.

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 resource, HTTP 410, and indicates the tool is about its meaning, so the general subject is clear. However, it lacks an operative verb such as 'returns' or 'explains', and it does not distinguish this tool from the sibling 'status-catalog' which likely also provides status-code meanings.

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 'status-catalog' or when to invoke it with the four provided parameters. There is no mention of exclusions, prerequisites, or contexts where another tool would be better.

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. The description does not mention that the tool likely reads a static registry, whether it mutates anything, what it returns, or that it relates to clock calls. There is no disclosed side effect, no mention of data sources, and no contradiction, but there is also zero behavioral information beyond the tool name.

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 (one fragment of seven words), which is economical, but it is under-specified rather than concise. It front-loads the only topic hint ('Common IANA timezone names'), but a single noun phrase cannot earn credit for structure when it omits any predicate that would make it usable. There is no wasted prose, but there is also no substantive content.

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, no output schema, and no usage guidance, this description is wholly inadequate. The tool likely deals with IANA timezone names, yet the schema includes url, host, and json parameters that are completely unexplained in relation to the tool's purpose, and there is no mention of what the tool returns or how the parameters interact. An agent has no basis to decide whether calling this tool is appropriate or how to populate its arguments.

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 every parameter (url, host, json, zone) has a description in the schema. However, the tool description itself is titled around 'iana timezone names' yet the schema contains four seemingly unrelated parameters (url, host, json, zone) with no indication of which parameters are actually relevant to this tool or how they relate to IANA timezone names. The schema descriptions are generic ('HTTPS URL to normalize or cite', 'JSON text to validate') and do not clarify how they apply to a timezone-name tool, so the description fails to add the semantic glue the agent needs.

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 fragment, not a sentence with a verb. It does not state what the tool actually does (e.g., validates, lists, or references timezone names). It also fails to distinguish itself from the sibling tools (citation, compatibility, etc.), which are functionally unrelated but the description gives no operation or resource the agent can act on. The name 'iana-zones' is the only real signal, making this close to a tautology with only a vague hint about content.

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 any alternative. The description lacks a verb, so it cannot state a condition such as 'use this when you need to validate a timezone name' or 'for citations, use the citation tool instead'. With four sibling tools present and zero usage context, 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, the description carries the behavioral disclosure burden. It does reveal that the tool returns only group counts, which is useful, but it says nothing about failure behavior, missing robots.txt files, redirects, or which parameters are ignored. The disclosure is minimal but not misleading.

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

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

The description is a single, front-loaded sentence with no filler. It states the resource, the action, and the restricted output in a compact way.

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

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

The tool is not complete enough to invoke correctly: there is no output schema, no annotations, no explanation of what 'group counts' means, and no clarification of how the four optional parameters relate to robots.txt inspection. The unrelated schema and missing usage context leave significant gaps.

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 has 100% description coverage, but the parameter descriptions are unrelated to the tool's stated purpose: 'url' is described as 'HTTPS URL to normalize or cite', 'json' as JSON text to validate, and 'zone' as a timezone name. The main description never maps any parameter to the robots.txt target, making the parameters effectively misleading rather than helpful.

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 ('Fetch a public robots.txt') and the precise output ('return group counts only'), so an agent can tell what the tool does. It does not explicitly differentiate from siblings, but the robots.txt resource is distinctive enough among the listed 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 on when to use this tool versus alternatives such as domain-shape, http-410, or normalize-url. The description gives no context, prerequisites, or exclusions, leaving the agent to infer the appropriate use case.

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

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

The description adds a concrete behavioral guarantee by noting that query and fragment are dropped. However, with no annotations, it does not disclose how the extra parameters are handled, whether the operation has side effects, or what happens on invalid input.

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 tight sentences with no filler, and the key transformation behavior is front-loaded. It is concise, though the brevity leaves important schema-related questions unanswered.

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 annotations, and no output schema, this description is incomplete. It does not explain the relationship of host, json, and zone to the operation, describe the return shape, or cover error/validation behavior.

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

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

Schema description coverage is 100%, so the baseline is 3 even without additional parameter detail in the tool description. The description adds no parameter semantics, and schema labels like 'json' and 'zone' feel disconnected from the stated URL-normalization purpose, but they are at least minimally described.

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: return origin, host, and path for a URL, and explicitly says query and fragment are dropped. It is clear and not a tautology, though it does not address the unrelated schema parameters (host, json, zone) or compare with 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?

No when-to-use or when-not-to-use guidance is provided. There are no stated alternatives, prerequisites, or conditions that would help an agent decide between this tool and another.

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 discloses no side effects, return shape, rate limits, prerequisites, or processing semantics, and it conflicts with the schema's implication that the tool performs multiple unrelated operations. The phrase "catalog" is too weak to count as behavioral disclosure.

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 it is an under-specified noun phrase rather than a helpful, structured explanation. It front-loads nothing actionable and omits essential information about the tool's interface or behavior.

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

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

With four parameters, no output schema, no annotations, and a heterogeneous set of sibling tools, this description is completely inadequate. An agent cannot determine what action to take, what inputs to provide, or what response to 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 each parameter has a clear description in the schema itself. However, the tool description adds no meaning to these parameters and fails to connect them to the stated HTTP status code catalog purpose, leaving the overall semantics 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 "Short catalog of common HTTP status codes" is essentially a restatement of the tool name and provides no verb or operation. It does not explain what the tool does with the supplied url, host, json, or zone parameters, and it does not distinguish this tool from siblings like http-410 or normalize-url.

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 its alternatives. The description suggests a tool about HTTP status codes, while the schema clearly points to URL normalization, JSON validation, and timezone handling, which is misleading for an agent trying to select the right tool.

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 only states what the tool returns and does not explain validation of the zone, output format, error behavior, or how the unrelated schema parameters relate to the tool's 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 a single, short sentence with no filler. It is front-loaded and easy to parse, making it appropriately concise for the stated purpose.

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

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

The tool has no annotations and no output schema, and its schema contains four optional parameters that are largely unrelated to the stated purpose. The description does not explain what an agent should pass, what the response looks like, or how to handle the extraneous parameters, leaving too much ambiguity 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%, providing a baseline of 3, but the description only aligns with the 'zone' parameter. The schema also includes 'url', 'host', and 'json', which are irrelevant to a timezone lookup and the description does not clarify their purpose or whether 'zone' is effectively required despite being optional.

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

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

The description clearly identifies the resource: current time in a named IANA timezone. It distinguishes this from the sibling utc-time by requiring a named timezone, though it lacks an explicit verb like 'get' or 'return'.

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 that this tool should be used when a current time for a specific IANA timezone is needed. However, it does not explicitly mention alternatives such as utc-time for UTC, nor does it state when not to use this tool.

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, and the description discloses no behavioral traits beyond the bare output. It also fails to explain why the input schema contains four seemingly unrelated parameters (url, host, json, zone) that have no obvious connection to 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?

The description is short and contains no filler words, but it is also extremely sparse. It lacks any structural elements like examples, parameter explanations, or usage scenarios, so the conciseness is not accompanied by useful structure.

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

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

With four optional parameters of unclear relevance, no output schema, and no annotations, the description is severely incomplete. An agent cannot determine what arguments to pass, what the response looks like, or how this tool relates to the sibling time-related 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 the schema provides 100% description coverage, the parameters themselves are irrelevant to the stated purpose of returning a UTC timestamp. The description adds no clarification about what these parameters do or why they exist, leaving the agent with a confusing and incongruent parameter list.

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' is essentially a restatement of the tool name 'utc-time' with no verb or behavioral detail. It gives minimal information about what is returned, and it does nothing to differentiate this tool from siblings like 'timezone' or 'iana-zones'.

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. Sibling tools such as 'timezone' and 'iana-zones' are completely unaddressed, leaving an agent to guess which 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?

Annotations are absent, so the description carries the full burden. It does disclose one valuable trait — 'The body is discarded' — signaling that this is a side-effect-free check with nothing persisted. However, it omits the return contract: an agent cannot tell whether invalid JSON yields a boolean, an error, or diagnostic details, and there is no output schema to compensate.

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 front-loaded and the consequence ('discarded') stated immediately after. There is no filler, and every word contributes to either the purpose or the side-effect disclosure.

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 and no output schema, the description must establish the full contract, but it omits the return behavior for invalid JSON. Combined with a schema where three of four parameters appear orphaned from sibling tools, the description leaves an agent to guess which input matters and what the tool will produce, which is inadequate even for a simple validator.

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%, which sets a baseline of 3, but the description adds nothing the schema lacks: 'The body is discarded' merely restates the json parameter's own 'discarded after the check'. It introduces the inconsistent term 'body' instead of the actual parameter name, and it fails to clarify that url, host, and zone are irrelevant — precisely the clarification that would add value here.

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 ('Check') and resource ('whether a body is valid JSON'), and no sibling tool name suggests JSON validation, so it is naturally distinguishable from citation, normalize-url, timezone, etc. The main deduction is terminology drift: the description says 'body' while the schema parameter is named 'json', a small ambiguity that an agent must resolve.

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, when-not-to-use, or alternative-tool guidance is provided. More seriously, the schema exposes four parameters (url, host, json, zone) with zero required, and the description gives no hint that only json matters — leaving an agent uncertain whether to supply a URL, hostname, or timezone alongside the JSON text.

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