Kilograms to pounds

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add one useful fact — 'Page content is not stored' — which signals a privacy-safe operation. However, it does not disclose whether a live HTTP request is made, how redirects are handled, or what happens on failure, which are material for a network-touching tool.

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 compact sentences with the core result front-loaded. The second sentence adds a meaningful privacy constraint without padding. Every word earns its place.

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

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

Given four parameters where three (host, json, zone) don't align with the described purpose, the description is incomplete. An agent cannot tell whether those parameters are inputs, outputs, or artifacts of a merged schema. There is no output schema and no explanation of return values beyond the three items mentioned.

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

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

Schema description coverage is 100%, so the schema already documents each parameter. The description itself adds no parameter meaning. Notably, the schema parameters host, json, and zone appear unrelated to the stated purpose of returning host/scheme/status, creating ambiguity that the description does not resolve.

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

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

The description uses a specific verb and resource: 'Return host, scheme, and HTTP status for a URL.' This clearly differentiates it from the validate-json sibling (JSON input) and normalize-url sibling (URL normalization), though it does not explicitly name them. The tool name 'citation' mismatches the described function, which slightly reduces clarity.

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 normalize-url or validate-json, and no mention of prerequisites or exclusions. The only extra sentence, 'Page content is not stored,' is a behavioral note, not usage guidance.

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 full responsibility for behavioral disclosure. It adds one meaningful fact—'No identifiers are retained'—but omits whether the tool performs network requests, has side effects, or returns a classification label, confidence, or status.

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 core purpose is front-loaded and the privacy note is a valuable addition that does not waste tokens.

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

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

The description is too thin for a tool with no annotations and no output schema. It fails to explain what 'classified' means, which of the four optional parameters drive the classification, and what the agent can expect back. An agent would struggle to use this tool correctly without more context.

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

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

Schema description coverage is 100%, so all four parameters are already documented in the schema. The description adds no parameter-specific meaning—'this request' is a generic reference that does not map to url, host, json, or zone.

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 verb and resource: 'Show how this request is classified.' It conveys the tool's core function without being a tautology. However, it does not differentiate from siblings like citation or validate-json, and the meaning of 'classified' (compatibility vs. other categories) is left somewhat open.

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

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

There is no guidance about when to use this tool versus alternatives. No conditions, exclusions, or sibling comparisons are provided; the description only states what the tool does, not when an agent should reach for it.

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

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

No annotations are provided, so the description must disclose behavior on its own. It explains what data the tool omits, but not what it returns, how it handles the four different inputs, or whether it performs any validation or transformation beyond splitting.

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, and the main behavior is front-loaded. The phrase 'without WHOIS or ownership data' earns its place by setting expectations, though the brevity leaves some contextual gaps.

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 output schema, and no annotations, this description is too sparse to fully guide invocation. It does not explain how the parameters relate to the operation or what result an agent should expect, leaving significant room for misinterpretation.

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

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

Schema description coverage is 100%, so the input schema already documents url, host, json, and zone. The tool description adds no parameter-level meaning and actually creates ambiguity by talking only about hostname splitting while the schema lists unrelated optional 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 clear operation: 'Split a hostname into labels', which is specific and actionable. It also adds a useful boundary by saying 'without WHOIS or ownership data', which helps distinguish it from enrichment-style domain 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 implies when to use the tool: when hostname labels are needed and WHOIS or ownership data is not. However, it does not explicitly state when not to use it or point to sibling alternatives, so the guidance is more implicit than explicit.

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. The description adds minimal context (that these are 'common' IANA timezone names and are intended for 'clock calls'), but it omits what the tool does, what it returns, or any side effects. For a tool likely returning a static list, the description discloses almost nothing about behavior.

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

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

The description is short, which is good, but it is under-specified. A single phrase 'Common IANA timezone names for clock calls' gives almost no operational information; this is not genuine conciseness but a lack of substance.

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 four parameters that appear mutually unrelated, an agent has insufficient context to call this tool correctly. The description provides no mention of return values, use case, or parameter relationships. This is severely incomplete.

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%, four unrelated parameters (url, host, json, zone) are documented in the schema but none are described as optional or required based on use case. The description says 'timezone names for clock calls', which hints that the 'zone' parameter is relevant, but it does not clarify which parameters apply to this tool or how they relate to each other. With full schema coverage, a baseline of 3 is appropriate, but the description adds little semantic meaning.

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

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

The description 'Common IANA timezone names for clock calls' describes a static list of timezone names, not an actionable tool operation. It has no verb indicating what the tool does; there is no way for an agent to know whether this tool returns a list, filters, or performs some action. The name 'iana-zones' is about as informative as the description, so this is close to a tautology.

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 about when to use this tool versus siblings like 'citation'. The description mentions 'clock calls' but does not explain how an agent would use this list of timezone names or when it would be relevant. An agent cannot decide between this and the sibling tools from the 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?

With no annotations, the description carries full behavioral disclosure. It notes the 'group counts only' limitation, but does not disclose that a network fetch occurs, how failures are handled, or that parameters like json and zone appear unrelated to the robots.txt purpose. The schema hint that json is 'discarded after the check' is not reflected in the main description, creating uncertainty.

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 with zero filler. Every word earns its place and the key output constraint ('group counts only') is stated immediately.

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 parameters, 0 required, no annotations, and no output schema, yet the description does not explain what to pass, what 'group counts' means, or why json/zone parameters exist. The schema is actively misleading, and the description is far too thin to let an agent invoke this tool correctly.

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

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

Schema coverage is 100%, so a baseline of 3 applies, but the schema descriptions are generic and mismatched with the tool's purpose (url is 'to normalize or cite', json to 'validate', zone as 'IANA timezone'). The description does not clarify how url/host map to the robots.txt fetch or whether json/zone are ignored, so it fails to add meaningful parameter guidance despite high nominal coverage.

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?

Always says a specific verb (fetch), a resource (public robots.txt), and a precise outcome (return group counts only). This clearly distinguishes it from unrelated siblings like citation, normalize_url, status_catalog, timezone, and validate_json without needing explicit contrasts.

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 usage is implied: use it when you need group counts from a public robots.txt. However, it does not state when not to use it, list prerequisites (e.g., public accessibility), or mention any alternative approach, leaving the agent to infer applicability from the short sentence alone.

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

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It reveals no side effects, return format, validation rules, or how any input is used, and its only behavioral claim is unsupported 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, but brevity here is under-specification rather than effective conciseness. It omits the essential input/output contract and does not convey enough information to stand alone as a usable 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 four-parameter tool with no output schema and no annotations, a single implied phrase is grossly incomplete. There is no mapping between parameters and the conversion, no expected return value, and no connection to the sibling tools that could help an agent select or invoke this tool correctly.

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

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

Although the schema descriptions are self-explanatory for url, host, json, and zone, none of these parameters accepts a mass value, and the description does not explain how kilograms would be supplied. An agent cannot determine which parameter maps to the stated conversion, so the parameter semantics are effectively unusable.

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 'Kilograms to pounds' essentially restates the tool name kg-to-lb in expanded form, adding no verb or operational detail. It implies a conversion purpose but the input schema exposes url, host, json, and zone parameters that are unrelated to mass conversion, making the stated purpose unclear and practically 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?

There is no guidance on when to use this tool, what inputs are needed, or when to prefer a sibling tool. Worse, the description's implied use case—kg-to-lb conversion—has no corresponding parameter anywhere in the schema, so an agent following the description would be misled about how to invoke the 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?

The description transparently discloses that query and fragment are dropped and that the result contains origin, host, and path. However, with no annotations, it does not cover behavior for the other parameters, invalid URLs, rejected inputs, or the exact return shape, leaving some important behavior undocumented.

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 deliver the core purpose and the most important transformation rule with no filler. Each sentence earns its place and the key output 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?

With four optional parameters, no output schema, and no annotations, the description is too narrow: it only explains URL normalization and leaves other parameters and invocation modes unexplained. An agent cannot confidently determine what happens when json, host, or zone is provided, or what a valid call looks like.

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 meaning to the url parameter by saying it is normalized into origin/host/path. But it adds no semantic clarity for host, json, or zone, which the schema describes but the description never connects to the tool's 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 clear verb and resource: it returns origin, host, and path for a URL, and explicitly drops query and fragment. This is specific enough to separate it from generic 'normalize URL' wording, though it does not explicitly distinguish it from the 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 gives no guidance on when to use this tool versus alternatives like get-document-metadata or parse-date. It also does not explain how the unrelated optional parameters (host, json, zone) should be used or whether they represent alternative modes.

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 discloses nothing. It does not state what the tool does with the inputs, whether it performs network requests, what side effects occur, or what the output looks like. The description is merely a label, not a behavioral explanation.

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

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

The description is a single short sentence, which is compact, but this is under-specification rather than effective conciseness. It front-loads nothing of value and omits all operational detail, so brevity does not earn credit.

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

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

Despite 100% schema parameter coverage, the description is far too thin to make the tool usable. The contradiction between the stated catalog purpose and the actual parameters is unresolved, and with no output schema or annotations, an agent has no way to know what to pass, what to expect back, or how this differs from 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 description coverage is 100%, so each parameter already has a written explanation in the schema. The description adds no meaning beyond the schema, which yields the baseline score of 3. However, the description does not help resolve the puzzling mismatch between a 'status code catalog' and parameters like url, host, json, and zone.

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 tautology that restates the tool name 'status-catalog'. It uses a noun phrase rather than a verb+resource structure, and it does not distinguish this tool from siblings like citation or compatibility. The description also conflicts with the actual parameters (url, host, json, zone), which have no evident connection to a status-code catalog.

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 whatsoever about when to use this tool versus its siblings. The description does not mention any scenario, prerequisite, or context in which an agent should invoke status-catalog, nor does it explain how the parameters relate to the stated purpose.

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 full responsibility for behavioral disclosure. It only states the basic function and does not mention return format, DST handling, invalid-zone errors, or that the unrelated schema parameters (url, host, json) are presumably ignored or irrelevant.

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 eight-word sentence with no filler, front-loading the action and resource. It is appropriately concise and every word earns its place.

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

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

For a tool with no annotations and no output schema, the description is incomplete. It does not specify how to provide the zone via the schema, what the returned time format is, how errors are handled, or why the other optional parameters exist. An agent would likely call it correctly but without confidence about edge cases.

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 extra meaning about the parameters themselves and does not explicitly map the 'zone' parameter to the described behavior, despite that being the crucial parameter for this tool.

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: 'Current time' in a 'named IANA timezone'. This clearly identifies the tool's function and helps distinguish it from sibling tools like utc-time, which likely returns UTC time without a zone argument.

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—whenever a current time for a named IANA timezone is needed—but it gives no explicit exclusions, alternatives, or comparison to sibling tools. Usage context is readable but not directly stated.

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. 'Current UTC timestamp' states the core operation and timezone, and there is no contradiction, but it does not disclose the output format (e.g., ISO 8601 vs epoch seconds) or any other observable behavior. This is adequate for a trivial read-only tool but not informative beyond the bare claim.

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 three-word phrase with zero wasted words. It is highly efficient, though slightly under-sized given the unexplained parameter set and absent output details.

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 (url, host, json, zone) that are not obviously related to returning a UTC timestamp, no output schema, and no annotations. The description does not clarify how these parameters relate to the tool's behavior, what format the timestamp is returned in, or what the agent should expect from the response. A tool this simple still needs at least a sentence connecting the parameters or specifying the output 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 already documents all four parameters (url, host, json, zone). The description adds no parameter-level meaning, and it notably fails to explain why a UTC-time tool has these unrelated optional parameters. Baseline 3 applies because the schema handles the parameter documentation.

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

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

The description 'Current UTC timestamp' clearly identifies the tool's resource (a UTC timestamp) and its current/now semantics. It is nearly a restatement of the tool name 'utc-time', but 'current' adds the key temporal meaning, and none of the sibling tools (citation, compatibility, domain-shape, iana-status, screenshot, user-agent) compete with this purpose.

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, and no exclusions or prerequisites are stated. There is no explicit when-to-use or when-not-to-use context anywhere in the 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?

With no annotations, the description carries the full disclosure burden. It does disclose a meaningful side effect ('The body is discarded'), implying the operation is non-mutating and stateless. However, it does not say what happens for invalid JSON (error vs false), what output the agent should expect, or whether the url/host/zone parameters influence 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?

Two short sentences with zero filler and the core action front-loaded. The second sentence earns its place by disclosing disposal behavior. Slightly stronger wording would use 'json' instead of 'body' to align with the schema.

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

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

Given 4 parameters, no required fields, no output schema, and no annotations, the description is incomplete. It explains only a single action loosely, gives no clue why url, host, and zone exist, and does not state the return or error contract an agent needs to act on the result.

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

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

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter-level meaning beyond the schema, and worse, it calls the input 'body' while the schema calls it 'json', and the unrelated url/host/zone descriptions do not connect to JSON validation. The description fails to resolve which parameter is actually 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 names a specific verb ('check') and resource ('a body') and clearly states the tool validates JSON. However, 'body' is ambiguous next to the schema's only relevant parameter, 'json', and the three unrelated parameters (url, host, zone) obscure what is actually being validated. It does not distinguish itself from sibling tools, whose names appear unrelated ('normalize', 'cite', 'timeout', 'sleep').

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, what prerequisites exist, or what inputs are expected. The presence of unrelated parameters with no explanation leaves the agent guessing which parameter combination constitutes the 'body'.

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