Celsius to Fahrenheit

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

The description discloses one behavioral trait ('Page content is not stored'), which is useful, but annotations are absent, so the burden falls on the description. It fails to disclose that json and zone inputs appear to be accepted but unexplained, creating confusion about the tool's real 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 and front-loaded, but under-specification is not true conciseness. A single sentence for a tool with four unrelated-looking parameters (url, host, json, zone) omits critical information that the sentence should have earned its place by providing.

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 spanning URL handling, JSON validation, and timezone data, plus no output schema and no annotations, this one-sentence description is seriously incomplete. It does not explain what the tool actually does with json and zone, leaving an agent unable to invoke 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?

The input schema provides descriptions for all 4 parameters, so 100% coverage gives a baseline of 3. The description adds little beyond the schema—'host, scheme, and HTTP status' loosely relates to url and host, but it does not clarify json or zone semantics.

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 function ('Return host, scheme, and HTTP status for a URL'), which gives a clear verb+resource for a core use case. However, it does not account for the json and zone parameters in the schema, so the overall tool purpose is ambiguous and not fully distinguished from potential 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?

No guidance is provided on when to use this tool versus alternatives. The description simply states what it does without mentioning conditions, exclusions, or suitable contexts for URL citation versus other possible 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 the full burden of behavioral disclosure, and it does add some value: 'No identifiers are retained' is a meaningful privacy behavior, and 'Show' implies a non-mutating operation. However, it does not disclose whether network calls occur, what side effects exist, or what the classification output looks like.

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

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

Two short sentences with no filler, and the main assertion is front-loaded. It is appropriately concise for the small amount of information it conveys, though the first sentence is vague enough to limit overall usefulness.

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

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

With no output schema and no annotations, the description should define the classification categories, input requirements, and expected result. It provides none of these, so an agent cannot predict what the tool returns or which of the four optional parameters should be supplied.

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 description does not explain how url, host, json, or zone map to the classification, leaving the agent to rely on the schema property descriptions.

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

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

The description uses a verb and object ('Show how this request is classified'), but 'classified' is undefined and the tool name 'compatibility' is not reflected in the description. It does not differentiate this tool from siblings like validate-json, normalize-url, or timezone.

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 ten siblings. The description implies a classification use case but provides no conditions, exclusions, or explicit alternatives.

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, and 'Celsius to Fahrenheit' only names a conversion. It reveals nothing about the parameters it actually accepts, the return format, or whether the operation is pure; the mismatch with the schema further obscures real 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?

Four words are concise, but this is under-specification rather than effective concision. The description is a single phrase with no details, so there is no meaningful structure or front-loaded substance beyond a restatement of the name.

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 optional parameters, no output schema, and no annotations, the description must explain what the tool does with those parameters and what it returns. It does neither, and the schema mismatch makes the definition dangerously incomplete for correct invocation.

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

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

The schema gives each parameter its own clear description (100% coverage), so the baseline is not zero, but the tool description provides no mapping from `url`/`host`/`json`/`zone` to the stated conversion. An agent is left with individually understandable parameters whose collective purpose is unknown.

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

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

The description is essentially the tool name written out ('Celsius to Fahrenheit') and still describes no operation that connects to the input schema. It is not just vague but misleading, since the schema exposes only `url`, `host`, `json`, and `zone` and no temperature-related input.

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 usage guidance, prerequisites, or alternatives are given. The implied use case (temperature conversion) is contradicted by the schema, so the agent cannot reliably decide when to call this tool instead of a sibling such as `timezone`, `validate-json`, or `normalize-url`.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that the tool does not provide WHOIS or ownership data, which is a behavioral limit. However, it does not describe what happens to the 'json' parameter (stated as 'discarded after the check' in the schema), input validation behavior, or any edge cases around hostname format handling.

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 with zero wasted words. It is front-loaded with the primary action ('split a hostname into labels') and immediately follows with the key exclusion ('without WHOIS or ownership data'). No unnecessary elaboration.

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 (all optional), no output schema, and no annotations. The description explains the core purpose but does not clarify why a tool that splits hostnames would accept a 'url', 'json', and 'zone' parameter. Without an output schema or richer behavioral details, an agent may be uncertain about which parameters to supply together and what the return value 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 schema already documents all four parameters. The description adds the top-level behavioral context that the tool splits hostnames into labels and does not do WHOIS/ownership lookup, which helps the agent understand the tool's intent. While the description does not explain each parameter individually, the schema fully covers this, making the combination solid.

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 'Split a hostname into labels without WHOIS or ownership data' uses a specific verb ('split') and resource ('hostname'), and explicitly states what it does NOT do (no WHOIS or ownership data), which distinguishes it from tools that might fetch domain registration or ownership information. This makes the purpose clear and unambiguous.

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 implicitly suggests this tool is for hostname label splitting rather than WHOIS lookups or ownership queries, but it does not explicitly state when to use this tool versus alternatives. There is no mention of scenarios where it would be more appropriate than sibling tools, nor any exclusions for when not to use it.

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

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

With no annotations provided, the description must carry the full behavioral burden, but it only says the tool contains common names. It does not disclose whether this is a read-only lookup, what it returns, whether it filters or validates zones, or any side effects.

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

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

The description is only a short noun phrase and is under-specified for a tool with four optional parameters and ten sibling tools. While there is no wasted text, the brevity sacrifices necessary operational clarity.

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

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

Given the lack of annotations, output schema, and explicit sibling differentiation, the description is not complete enough for reliable invocation. An agent cannot tell what action to take, which parameters apply, or what the tool returns.

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

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

The schema has 100% description coverage, so each parameter is individually documented and the baseline is 3. The tool description adds no parameter-level meaning, and the connection between url, host, and json versus IANA timezone names remains unclear, but the schema itself provides the required field semantics.

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 communicates the resource: common IANA timezone names for clock-related operations. However, it lacks a verb and does not state what the tool does with those names, making the purpose vague and close to a restatement of the tool name.

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 instead of the sibling tools like timezone, utc-time, or validate-json. The phrase 'for clock calls' hints at a context, but it never explicitly explains conditions or alternatives.

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 implies a read-only network fetch to a public resource, but it does not disclose error behavior, redirect handling, response shape, the fact that all rule details beyond group counts are discarded, or any access constraints. Minimal 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?

A single efficient sentence with the action and the limiting scope ('group counts only') front-loaded. 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 no output schema, no annotations, and four parameters whose documented semantics do not match the tool's stated purpose, an agent cannot reliably determine which parameters apply or what the response looks like. The one-sentence description is far too thin to compensate.

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 plainly copied from unrelated tools: 'JSON text to validate; discarded after the check' and 'IANA timezone name' have nothing to do with fetching robots.txt, and 'HTTPS URL to normalize or cite' describes a citation tool, not a robots.txt fetcher. The schema descriptions actively mislead rather than help.

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 ('Fetch'), a specific resource ('public robots.txt'), and a scope qualifier ('return group counts only') that differentiates it from a full robots.txt parse or a raw-fetch tool. An agent can tell what this tool does in one sentence.

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, no conditions, and no exclusions. There is no routing information at all beyond the implied robots.txt 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?

With no annotations, the description carries the full burden and does disclose at least one meaningful behavior: query and fragment are discarded. But it is silent on error handling, invalid inputs, and behavior when the url parameter is omitted, leaving the behavioral profile incomplete.

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, front-loaded with the primary behavior and zero filler. The most important constraint is stated immediately, making it easy to parse.

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

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

For a tool with no annotations, no output schema, and four parameters, the description is too thin. It explains only the url behavior, leaves host, json, and zone disconnected from the tool's purpose, and offers no return-structure details beyond naming origin, host, and path.

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 a small detail beyond the schema (dropping query/fragment), but it does not clarify what host, json, and zone have to do with URL normalization, leaving those parameters semantically confusing.

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 core behavior: return origin, host, and path for a URL, and explicitly notes that query and fragment are dropped. That is a specific verb+resource pairing. It loses a point because it does not differentiate from sibling tools, and the schema includes seemingly unrelated parameters (json, zone) that muddy the tool's 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?

Usage is implied: call this when you need origin/host/path from a URL and want query/fragment removed. However, there is no explicit when-not-to-use guidance, no mention of alternatives, and no direction on what to do with the non-URL parameters.

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, but it only describes the catalog as 'short' and about 'common HTTP status codes.' It does not disclose whether this is a read-only lookup, what the output shape is, whether inputs affect the result, or what side effects exist.

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

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

The description is only one sentence and is concise, but it is under-specified rather than efficiently informative. It gives a topic sentence without actionable detail, so while it is short, it does not fully earn its place.

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

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

The tool has four optional parameters, no required parameters, no output schema, and no annotations. The description provides enough context to guess the domain but not enough for an agent to know how to call the tool, what response to expect, or how inputs influence 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?

The input schema has 100% description coverage and clearly documents url, host, json, and zone. However, the tool description adds no information connecting these parameters to the status-code catalog, so the agent cannot determine which parameters, if any, should be supplied.

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 does not use an operational verb or state what the tool does with its inputs. It identifies a topic, but not an action, and it does not clarify whether the tool returns definitions, filters a list, or performs a lookup.

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 its siblings such as citation, normalize-url, or validate-json. The description also fails to mention whether any of the four optional inputs are relevant or how to invoke the catalog.

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

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

With no annotations, the description bears the full burden of disclosing behavior, but it only states the output concept. It does not explain what happens for invalid or unknown zone names, whether the time is fetched at call time, what format is returned, or that unrelated schema fields are ignored.

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

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

The description is a single, focused sentence with no filler and the key purpose front-loaded. It is appropriately terse, though the brevity contributes to the missing usage and behavior guidance.

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?

Although the core behavior is simple, the description is incomplete in context: no annotations, no output schema, and a parameter list containing several fields unrelated to timezones. The agent is not told which parameter to populate, how ignored fields are handled, or what the response 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 coverage is 100%, so the baseline is 3. The description adds no new parameter meaning beyond the zone property's existing 'IANA timezone name' text, and it does nothing to disambiguate the three extraneous-looking parameters (url, host, json), leaving selection of the right input 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 clearly states the tool's function: returning the current time for an IANA timezone. This distinguishes it from sibling tools like utc-time (UTC) and iana-zones (listing zones), though it lacks an explicit verb and relies on the tool name for full 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 utc-time or iana-zones, and no mention of validating the zone. The phrase 'named IANA timezone' implies a zone input is needed, but the description never directs the agent to the zone field.

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, but it only states 'Current UTC timestamp.' It does not disclose output format, precision, determinism, side effects, or how the four optional schema parameters are handled. This is minimal 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 extremely concise and front-loaded with the essential concept. There is no wasted text, though the brevity 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 description is incomplete for a tool with an unrelated four-parameter schema and no output schema. It omits the return format, the meaning of the irrelevant-looking parameters, and any relationship to sibling time tools, leaving important ambiguity for an agent deciding 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?

The input schema lists four optional parameters (url, host, json, zone) with descriptions unrelated to UTC time. The tool description does not reconcile these parameters with the stated purpose, leaving the agent to wonder if they are ignored, deprecated, or part of a misconfigured shared schema. This is actively 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 identifies the resource ('UTC timestamp') and the operation ('current'), making the core purpose reasonably clear. It is distinguishable from sibling tools like timezone and iana-zones, though it lacks an explicit verb such as 'return' or 'get'.

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 related siblings like timezone or iana-zones. An agent cannot determine whether this is for the current instant, timezone conversion, or timezone listing without relying on guesses.

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

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

With no annotations, the description carries the full burden, and it does disclose one meaningful behavioral trait: 'The body is discarded.' This tells the agent the input is consumed and not retained. However, it omits critical behavior for a validation tool—what happens on invalid JSON (returns a boolean? throws? produces an error report?)—and discloses no other side effects.

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 a key behavioral caveat with zero filler. The primary action is front-loaded, and the discard warning earns its place because it changes how an agent should think about the call.

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, no output schema, and no annotations, the description is too sparse to be complete. It doesn't explain the irrelevant-looking url/host/zone parameters, doesn't specify the return value or error handling for invalid JSON, and offers no guidance on how this tool relates to the siblings. An agent would likely be confused about which parameters to populate.

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 reinforces that the 'json' parameter's content is discarded, matching the schema's 'discarded after the check.' Yet the schema's other parameters (url, host, zone) have descriptions clearly copied from sibling tools ('HTTPS URL to normalize or cite', 'IANA timezone name'), and the tool description does nothing to clarify why they exist on validate-json.

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: 'Check whether a body is valid JSON.' The verb 'check' plus the resource 'JSON body' makes the tool's function obvious. It does not explicitly differentiate from the sibling tools (normalize, cite, status, timezone), but the purpose is self-evidently distinct from them.

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

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

Usage is implied: an agent would call this when it needs to verify whether some text is valid JSON. However, there is no explicit guidance about when to use this tool versus the siblings, no exclusions, and no mention of prerequisites or whether the tool is appropriate for large bodies.

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