HTTP 401 unauthorized

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 adds one useful note ('Page content is not stored'), but it does not disclose that the tool likely performs live network requests, potential side effects of hitting the URL, error behavior, or caching, which are important for a URL-checking 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?

The description is two crisp sentences, front-loading the core action and adding a privacy-relevant note with no fluff. It is appropriately sized, though the brevity comes at the cost of omitting the json/zone parameters.

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

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

The tool has 4 parameters, no output schema, and no annotations, which raises the completeness bar. The description explains one output shape (host, scheme, HTTP status) but omits how the json and zone inputs behave in the call, what the actual response looks like, and failure modes. An agent cannot fully plan an invocation from this description.

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%, but the description misaligns with the schema: it presents 'host' as an output while the schema defines 'host' as an input parameter ('Public hostname'). It also silently ignores 'json' and 'zone', so the description does not help an agent understand why those parameters exist or how they relate to the stated purpose.

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

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

The description states a specific verb and resource: 'Return host, scheme, and HTTP status for a URL.' This clearly distinguishes the core action. However, the input schema includes 'json' and 'zone' parameters that are entirely unmentioned, so the description does not cover the full purpose surface.

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

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

No guidance is given about when to use this tool versus its siblings, such as normalize-url or validate-json. The description says only what the tool does, with no context on selection criteria 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 provided, the description carries the full burden of behavioral disclosure. It adds one useful privacy guarantee ('No identifiers are retained'), but it does not state whether the tool performs network requests, has side effects, returns a classification label, or exposes any other behavior. This is insufficient for a tool accepting URLs, hosts, JSON, and timezone names.

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

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

The description is appropriately short: two sentences, with the main intent front-loaded and no filler. The privacy statement is a reasonable second sentence. The weakness is vagueness rather than verbosity or poor 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?

For a tool with four optional parameters, no output schema, and no annotations, the description is operationally incomplete. It does not explain what the classification output looks like, which parameters are relevant, what 'compatibility' means, or how this tool relates to the sibling tools. The 'No identifiers are retained' line provides useful but insufficient 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%, and each parameter already has its own description in the input schema, so the baseline is 3. The tool description itself adds no meaning about how url, host, json, and zone interact or which combination produces which classification, but it also does not need to repeat the schema's per-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 says the tool will 'Show how this request is classified,' which names an action and a vague resource ('this request'), but it never defines what classification means, what categories exist, or how 'compatibility' relates to the input fields. It also does not distinguish the tool from siblings like validate-json or normalize-url, so an agent cannot tell when this tool is the right one.

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 of the sibling tools, nor any mention of alternatives. The sentence 'No identifiers are retained' is a privacy note rather than a usage condition, and the description leaves unclear which of the four optional parameters should be supplied or under what circumstances.

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 transparency burden. It does disclose a meaningful trait — the operation is purely local and does not fetch WHOIS or ownership data — and 'split' implies a non-mutating transform. But it says nothing about how multiple inputs are handled, what happens to url/json/zone, or what the 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?

One tight sentence, front-loaded with the verb and resource, with zero filler. It is efficient but arguably under-sized for a tool whose schema exposes four seemingly unrelated inputs.

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 4-parameter, 0-required tool with no annotations and no output schema, a single sentence covering only hostname splitting is incomplete. Missing: what the 'labels' output looks like, whether url/host/json/zone are alternatives or combinable, and why JSON validation and timezone checking belong to the same 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, but the description does not add meaning beyond the schema and actively conflicts with it: it centers on 'hostname' while the schema's first and most prominent parameter is 'url', and it ignores json and zone entirely. The agent gets no help mapping behavior to 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 names a specific verb and resource ('Split a hostname into labels') and adds a scope contrast ('without WHOIS or ownership data'), which is clear for that one behavior. However, the input schema exposes url, json, and zone parameters — none explained by this sentence — so the stated purpose does not match the tool's apparent multi-input scope, and an agent cannot tell which input is actually meant to be used.

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 invoke this tool versus alternatives or on how to choose among url, host, json, and zone. The 'without WHOIS or ownership data' clause is a scope qualifier rather than a usage rule, and it names no sibling tool or exclusion condition.

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

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only hints that this is an informational lookup. It does not state whether network calls are made, what the function does with the url, host, json, or zone parameters, or what output format to expect, leaving the tool's behavior essentially opaque.

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 terse, but this is under-specification rather than effective conciseness. It contains only a definition-like phrase and lacks any operational detail, constraints, or context that would help an agent invoke the tool correctly.

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

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

The tool has no output schema, no annotations, four optional but unexplained parameters, and a description that mismatches the schema's apparent functionality. An agent is missing essential information about return values, parameter roles, and selection criteria, making the definition inadequate.

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

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

The schema provides descriptions for all four parameters, meeting the high-coverage baseline. However, the description does nothing to connect those parameters to the stated purpose of explaining HTTP 401, so an agent cannot tell how url normalization, JSON validation, or timezone data relate to the tool's function.

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, "Meaning of HTTP 401," is a noun phrase that restates the tool name rather than stating an operation on a resource. It gives no verb or action, and it fails to differentiate this tool from the sibling status-catalog, which likely covers HTTP status meanings more broadly.

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 status-catalog or the other sibling tools. There is no mention of scenarios, exclusions, or prerequisites, so an agent must guess whether this is a lookup, a validation step, or something else.

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 disclosing behavior, and it reveals almost nothing: no indication of whether the tool returns a list, enumerates options, validates input, or performs a lookup. It does not even state that calling it yields the zone names, despite the name implying a data resource.

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 redundancy, and the core subject ('Common IANA timezone names') is front-loaded. The phrase 'for clock calls' is slightly vague but not wasteful.

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 params, no annotations, and no output schema, the description is materially incomplete. It fails to explain what calling the tool returns, which parameters are meaningful to it, and how it relates to sibling 'timezone' and 'utc-time'. An agent would struggle to invoke it correctly or interpret its 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 coverage is 100%, so each parameter is individually described, meriting the baseline 3. However, three of the four parameters (url, host, json) appear irrelevant to a timezone-names tool and the description does nothing to clarify which parameters apply to this tool versus which are inherited from siblings. The mismatch leaves the agent guessing.

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 ('Common IANA timezone names') but uses no explicit verb, reading as a noun phrase rather than an action statement. The qualifier 'for clock calls' adds context but also confuses, since the tool name is about zones, not clock operations. It is distinguishable from sibling 'timezone' only by implication, not by explicit contrast.

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 choose this tool over siblings like 'timezone' or 'utc-time'. An agent cannot tell whether it should call iana-zones for a list of valid zones, or timezone for a conversion. No context or exclusions are provided.

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?

Without annotations, the description must carry the behavioral disclosure, and it only states that the tool fetches a public robots.txt and returns group counts. It does not explain behavior when robots.txt is absent, redirects, or how the unrelated 'json' parameter (described as 'discarded after the check') fits in, leaving the tool's actual behavior opaque.

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 a clear verb, resource, and scope qualifier; no words are wasted. Its brevity is a strength for parsing, even though the parameter mismatch reduces overall quality.

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 output schema, no annotations, and four optional parameters, the description must explain which parameters are meaningful for a robots.txt fetch and what 'group counts' means. It does neither, and the schema's unrelated parameters compound the gap, so an agent cannot reliably construct a valid call.

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%, every property description is irrelevant to the tool's stated purpose: URL normalization, public hostname, JSON validation, and IANA timezone. None of them explains how to target a robots.txt, so the high coverage actively misleads rather than helps; the description adds no parameter clarification.

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

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

The description states a specific action ('Fetch a public robots.txt') and limits the return value ('group counts only'), so an agent understands the core purpose. However, it does not explicitly differentiate from sibling tools like validate-json or timezone, though the robots.txt resource is distinctive enough to avoid confusion.

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 the sibling tools. It does not specify conditions, exclusions, or alternatives; the only signal is the implied use case of reading a public robots.txt, which is not enough to route an agent facing the sibling list.

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 discloses a concrete transformation: query and fragment are dropped. It also identifies the returned components. It does not cover error behavior or edge cases, but for a simple parser this is meaningful 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 one front-loaded sentence with no filler. The main behavior is stated first, and the important exclusion (query and fragment are dropped) follows 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 no annotations, no output schema, four optional parameters, and only a terse description. An agent is not told which parameter to populate, what the return structure looks like, or whether the extra schema parameters should be ignored. This is incomplete for safe 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?

Although schema description coverage is 100%, the schema exposes four unrelated optional parameters: url, host, json, and zone. The description only makes sense for url and does not reconcile how host, json, or zone relate to URL normalization. This is likely to confuse an agent into passing the wrong parameter.

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: 'Return origin, host, and path for a URL.' It also says what is excluded. It is clear and actionable, though it does not explicitly distinguish itself from sibling tools beyond the URL-focused phrasing.

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 use case is implied: use this tool when you need a URL's origin, host, and path without query or fragment. However, there is no explicit guidance about when not to use it, nor references to alternatives like get-ip or validate-json.

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 details, such as what it does with the inputs, whether it performs lookups, whether it returns a list, or whether any side effects occur. The description carries the full burden of disclosure and fails to meet it.

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 fluff or redundant information. It is front-loaded with the core phrase, but the lack of a verb and missing behavioral detail limit its value despite its brevity.

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 unrelated parameters, no output schema, and no usage guidance, the description is far too thin to enable correct invocation. An agent cannot determine what inputs are needed, what the output looks like, or whether any inputs are even relevant to the stated purpose.

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 have descriptions in the schema, which sets the baseline at 3. However, the description adds no meaning beyond the schema and does not clarify why URL, host, JSON, and zone parameters are relevant to a catalog of HTTP status codes.

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

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

The description is a noun phrase ('Short catalog of common HTTP status codes') that essentially restates the tool name without a verb indicating what action the tool performs. It does not distinguish the tool from siblings like citation or validate-json, and the relationship between the stated purpose and the URL/host/json/zone parameters is unclear.

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 or how it differs from the sibling tools. Nothing indicates what situation calls for status-catalog versus citation, compatibility, or validate-json, leaving the agent to guess.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the read-only lookup nature (getting the current time) but says nothing about output format, error handling, or invalid-zone behavior. It also fails to explain the presence of url, host, and json parameters in the schema, which appear unrelated to the stated purpose.

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, so it is concise. However, it is under-specified: it omits usage context and does not address the several parameters present in the schema. Under-specification is not true conciseness, so it does not earn a higher score.

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?

There is no output schema and no annotations, and the description leaves major gaps. The input schema contains three parameters (url, host, json) that are unexplained and appear mismatched with the timezone purpose. The description also does not state the response format or behavior for invalid IANA names. This is incomplete for a tool with such schema ambiguity.

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 description adds no parameter-level meaning beyond the schema. More importantly, the schema includes url, host, and json with descriptions unrelated to timezones, and the description does not clarify that only 'zone' is relevant. This ambiguity leaves agents unsure which parameters are valid for the intended operation.

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 function: 'Current time in a named IANA timezone.' It identifies a specific verb, resource, and scope. However, it does not explicitly distinguish this from the sibling utc-time tool, and the input schema includes unrelated parameters (url, host, json) that muddy interpretation.

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 alternatives. There is no mention of the utc-time sibling, no conditions, and no exclusions. The only hint about intended use is the 'zone' parameter in the schema, not 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the output concept but not the timestamp format, nor does it explain why the schema contains four unrelated optional parameters such as url, host, json, and zone. This ambiguity is a meaningful behavioral gap.

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

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

The description is very concise and front-loaded, but it is too terse to be fully effective. For a tool with a mismatched schema, a little more explanatory structure would materially improve the definition without sacrificing conciseness.

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?

There is no output schema, so the description should at least clarify the timestamp format and confirm whether any parameters are relevant. It does neither, and the unrelated optional parameters create avoidable ambiguity for an agent choosing and invoking the 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?

The schema has 100% description coverage, but every parameter description is unrelated to UTC time (e.g., 'HTTPS URL to normalize or cite', 'JSON text to validate'). The tool description adds no clarification about whether these parameters are accepted, ignored, or rejected, making the parameter semantics confusing 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 'Current UTC timestamp' clearly states what the tool returns: the current UTC time as a timestamp. It is a specific, recognizable purpose and distinct enough from siblings like iana-zones or timezone, though it does not explicitly differentiate itself 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?

There is no guidance on when to use this tool versus alternatives such as timezone or iana-zones. The description also does not mention whether parameters should be supplied or ignored, leaving usage entirely to inference.

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

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

The description does add one meaningful behavioral trait: 'The body is discarded,' indicating no persistence. However, with no annotations, it does not disclose what happens on invalid JSON (e.g., error vs. false return), whether the tool performs network fetches, or how the result is represented.

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 very concise: two short sentences with the core purpose front-loaded. The only minor issue is the ambiguous term 'body' instead of a more precise reference to the json parameter, which loses a fraction of 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?

For a tool with no output schema and no annotations, key behavioral details are missing: what the tool returns/emits for valid vs. invalid JSON, whether it accepts only the json parameter or also url/host/zone, and any error semantics. An agent could likely use it, but would have to make assumptions.

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 explanation beyond what the schema already says; in particular, it does not clarify how the 'json' parameter maps to the 'body' mentioned in the description.

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 action ('Check whether a body is valid JSON') and identifies the validated resource. However, 'body' is ambiguous and there is no explicit differentiation from sibling tools, though the name and action make the purpose reasonably obvious.

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 alternatives. Sibling tools such as normalize/cite are not mentioned, and there are no conditions, exclusions, or context hints to help an agent choose this tool.

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