Europe/Paris clock

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 usefully states what the tool returns (host, scheme, HTTP status) and adds a meaningful retention detail ('Page content is not stored'). However, it does not mention whether the request follows redirects, what errors or edge cases occur (invalid URLs, non-HTTPS), or any rate-limit or authorization constraints, leaving notable behavioral gaps for an unannotated 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 short sentences with zero filler. The primary outcome is front-loaded ('Return host, scheme, and HTTP status for a URL'), and the non-storage disclaimer is a concise secondary clause. Every word earns its place, and the structure is easy to scan.

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

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

For a tool with four parameters, no annotations, and no output schema, the description is too sparse. It does not explain how host, json, and zone relate to the stated URL-status purpose, what inputs are required or optional in practice, or what the caller should expect in terms of return structure or failure modes. The 'Page content is not stored' note is useful, but the overall context is incomplete for confident invocation.

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

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

Schema description coverage is 100%, so the baseline is 3 per the rubric. The description adds no meaning beyond the schema; it only references 'a URL,' while the schema already documents the url, host, json, and zone parameters individually. It does not clarify why an HTTP-status checker would accept a timezone or JSON text, which would have been valuable extra 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 verb and resource: 'Return host, scheme, and HTTP status for a URL.' This clearly conveys what the tool does and distinguishes it from content-fetching tools by adding 'Page content is not stored.' However, it does not explicitly differentiate it from sibling citation-related tools, and the name 'citation' is broader than the HTTP-status behavior described, causing slight ambiguity.

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. It implies usage through the stated behavior but never says 'use this when you need X' or 'instead of Y.' An agent would have to infer the appropriate context from the parameter schema and description 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?

The description discloses one meaningful behavioral trait: 'No identifiers are retained.' This is useful because the tool accepts a URL and JSON text. However, with no annotations provided, the description carries the full burden and still omits other important behavioral details such as whether the call performs external requests, whether it is read-only, or how the inputs are ultimately handled.

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 privacy note is placed prominently. However, it is too terse for a tool with four optional parameters, no output schema, and a set of overlapping siblings; the undefined term 'classified' makes the concision a source of ambiguity rather than 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 tool's four parameters, zero required fields, absent annotations, and missing output schema, the description is not complete enough for an agent to call it correctly. It fails to state what the classification result looks like, how the parameters combine, or what category labels or output format to expect.

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

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

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter-specific meaning beyond the global no-retention promise; the schema already documents 'json' as 'discarded after the check' and the other parameters individually. This is adequate but not enhanced by 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 uses a verb ('Show') and an object ('how this request is classified'), but never explains what 'classified' means or what the tool actually does with the inputs. It does not clearly differentiate from siblings like normalize-url or validate-json, so an agent could not confidently decide to invoke this tool for a URL, host, JSON payload, 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?

There is no guidance about when to use this tool versus alternatives such as citation, domain-shape, or validate-json. No conditions, exclusions, or prerequisites are stated, leaving the agent to guess the intended call context.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool avoids WHOIS/ownership data; it says nothing about side effects, permissions, rate limits, invalid input handling, or return behavior. The 'json' parameter's 'discarded after the check' behavior appears only in the schema, not in the description.

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

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

The description is a single, compact sentence that is front-loaded and easy to parse. It avoids fluff and clearly states the core action. However, given the breadth of the schema, a bit more structure or expansion would improve completeness without harming 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?

With four optional parameters of widely different types, no annotations, and no output schema, the description is not complete. It covers only the hostname-splitting aspect and leaves the purpose of url, json, and zone unexplained, so an agent cannot confidently predict the tool's full behavior or return values.

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 minimal meaning beyond the schema: it connects to 'host' but does not explain how url, json, or zone relate to the tool's behavior. The schema already documents each parameter, so the description does not need to repeat that, but it also does not clarify the mismatched parameter set.

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 ('Split a hostname into labels') and adds a useful exclusion ('without WHOIS or ownership data'). However, the input schema includes url, json, and zone parameters that are unrelated to hostname splitting, so the description leaves the tool's overall purpose ambiguous and may only describe one of several behaviors.

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. The phrase 'without WHOIS or ownership data' hints at a constraint but does not explain when to select this tool, what prerequisites exist, or how it differs from sibling 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool performs lookups, returns data, filters zones, makes network calls, or has side effects. The only behavioral hint is the ambiguous phrase 'for clock calls'.

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

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

The description is extremely short, but this is under-specification rather than effective conciseness. It is a single phrase with no structure, no actionable guidance, and no front-loaded operational information.

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 deeply incomplete for a tool with 4 optional parameters, no required parameters, no output schema, and no annotations. An agent cannot determine what inputs to provide, what the tool returns, or how it behaves. The unrelated-looking url, host, and json parameters only deepen the 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?

Schema description coverage is 100%, so the baseline is 3 even without parameter details in the tool description. However, the description adds no clarification about how url, host, and json relate to IANA timezone names, leaving the parameter set 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 is a noun phrase — 'Common IANA timezone names for clock calls' — with no verb or explicit operation. It largely restates the tool name (iana-zones) and adds only a vague 'for clock calls' hint that doesn't clarify what the tool actually does.

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. The sibling list contains plausible related tools like 'citation', 'inspect', 'normalize', and 'timezone', but the description never references them or provides any selection criteria.

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. It discloses the fetch behavior and that only counts are returned, but it omits the side-effect profile, error behavior for unreachable/non-public hosts, and implies a scope constraint (public') without defining it. The schema's json parameter ('discarded after the check') also hints at transient behavior that conflicts with the robots.txt framing.

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 – verb, object, scope, and output constraint are all present.

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?

High operational complexity: 4 parameters, none required, no annotations, and no output schema. The description does not explain how an agent selects the target site, what the return value looks like, why json/zone exist, or what happens when a robots.txt is missing. An agent would struggle to invoke the 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% giving a baseline of 3, but the description adds no mapping of parameters to the fetch operation – it does not say whether url or host is the site to fetch. Worse, the schema's own descriptions (normalize or cite, validate JSON, IANA timezone) appear mismatched with the tool's stated purpose, actively confusing which parameters an agent should populate.

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 (fetch) and resource (public robots.txt) with a clear output constraint (group counts only), which distinguishes it from the citation-themed siblings. However, 'group counts' is undefined, and the schema parameters (json, zone) suggest a different domain, which muddies the clarity even though the description itself is specific.

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 vs. the sibling citation tools, nor any when-not-to-use conditions. The phrase 'group counts only' implies a scope limitation, but it is not framed as usage guidance, so an agent has to infer applicability.

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 discloses one useful behavioral trait: query and fragment are dropped. With no annotations, the description carries the full transparency burden, so it should clarify behavior for the other parameters and error/validation cases. The schema hints at JSON validation and timezone handling that are completely undocumented in the description.

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

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

The description is a single sentence with no filler. The primary output is front-loaded and the dropped-components constraint is stated efficiently.

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 sufficient for a minimal URL-normalization tool, but the schema contains four parameters including unrelated types (host, json, zone) and there is no output schema. An agent cannot determine whether or how to use the other parameters. The description is incomplete for the actual tool surface.

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 a baseline of 3 is warranted. However, the description only addresses the url parameter and contradicts the presence of host, json, and zone by implying only URL input matters. This mismatch hurts semantic clarity rather than adding value beyond the schema.

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

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

The description clearly states the verb and output for a URL: 'Return origin, host, and path for a URL.' It also notes the query and fragment are dropped. However, the input schema includes host, json, and zone parameters that the description does not mention, so the described scope does not cover the tool's full surface. Sibling differentiation is also absent.

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 the many sibling tools (e.g., domain, status, validate-json). It also does not explain when to provide the host, json, or zone parameters. The context is entirely implicit.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only reveals that the catalog is 'short' and limited to 'common' codes. It does not explain what happens when the tool runs, what it returns, or why it accepts url, host, json, and zone parameters that are unrelated to HTTP status codes. This is a significant transparency 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 only five words and front-loaded, but this is under-specification, not conciseness. Given four parameters that appear unrelated to the stated purpose and no usage or behavior guidance, the description is far too sparse to earn high marks for appropriate sizing.

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 inadequate for correct invocation. It doesn't clarify what inputs to provide (all four parameters are optional and domain-mismatched to a status-code catalog), what triggers a useful call, or what the agent can expect back. An agent would struggle to select and call 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 description coverage is 100%, so the schema already documents each parameter (url, host, json, zone) with a one-line meaning, earning the baseline of 3. The description adds no parameter information at all, but it also doesn't need to for basic semantics; however, the parameters' relationship to the described purpose is left unexplained.

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 domain resource ('common HTTP status codes') and is distinguishable from the clearly different sibling domains (citation, timezone, validate-json). However, it lacks an action verb — it doesn't state whether the tool returns a list, a definition, or a lookup result — and 'catalog of ... status codes' largely restates the tool name 'status-catalog', though the added 'HTTP' and 'common' provide some scoping.

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 citation, compatibility, normalize-url, timezone, or validate-json. No context, prerequisites, or exclusions are given. An agent must infer use entirely from the name and 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 full burden of behavioral disclosure. It implies a read-only operation but does not confirm it, and critically, the schema lists three unrelated parameters (url, host, json) that contradict the tool's stated purpose. The description fails to disclose that these are likely irrelevant, making actual behavior ambiguous.

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 single sentence is succinct and front-loaded, but it is too terse given the schema's unrelated parameter list. A concise description would still clarify that only 'zone' is used or that other parameters are ignored; omitting that makes the brevity a shortcoming.

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 ambiguous four-parameter schema, no annotations, and no output schema, the description is incomplete. It does not explain how to invoke the tool, what response to expect, or why url, host, and json appear in the schema, leaving an agent uncertain about correct usage.

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 is minimally described. However, the description adds no extra meaning beyond the schema's 'IANA timezone name' for zone, and it does not resolve why non-timezone parameters exist. The baseline of 3 applies, but the confusing parameter set is not clarified.

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: 'Current time in a named IANA timezone.' This is specific enough to understand the tool's primary function. It does not explicitly differentiate from sibling tools like normalize or validate, but the operation is 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?

No guidance is given on when to use this tool versus alternatives, nor are prerequisites or error conditions mentioned. The description says nothing about which parameter to supply or how to handle invalid timezone names, 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?

No annotations exist, so the description must carry the behavioral disclosure burden. It implies a read-only time query but does not mention return format, parameter dependencies, or any operational characteristics. This is minimal and non-misleading, but far from transparent.

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

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

A single short sentence that is immediately clear and front-loads the purpose. No filler or redundant wording; it earns its place as a concise statement of intent.

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?

Without annotations, an output schema, or sibling differentiation, the description leaves ambiguity about whether the zone parameter is required, ignored, or optional, and how this tool differs from timezone/utc-time. An agent cannot reliably determine invocation 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 the baseline is 3. The description adds no information about how url, host, json, or zone relate to the tool's purpose, but the schema already defines each parameter adequately.

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 ('Current local time') and resource ('Europe/Paris'), making the core function clear. However, it does not distinguish this tool from siblings like timezone or utc-time, which likely serve similar purposes.

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 timezone, utc-time, or iana-zones. The description states only what it does, with no mention of alternatives or exclusion conditions.

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 behavioral burden. It communicates that the tool returns the current time in UTC and implies a side-effect-free read operation, which is useful. However, it does not state the output format (e.g., Unix seconds vs ISO 8601) or explain how the accepted inputs affect 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 four words and contains no filler or redundant phrasing. It is appropriately sized for a trivial utility that simply reports the current UTC time.

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 having 4 optional parameters and no output schema, the description does not clarify what kind of timestamp is returned or how parameters like url, host, json, or zone are used. An agent cannot tell whether passing zone changes the result or whether the other parameters are ignored.

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 already described in the schema, which sets a baseline of 3. The description adds no additional meaning about how the four optional parameters relate 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 'Current UTC timestamp.' is essentially a restatement of the tool name 'utc-time' in noun phrase form, with no verb and no elaboration on what the agent should do with it. It does not distinguish this tool from siblings like timezone or tz-europe-paris.

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 timezone-related tools, no mention of required arguments, and no indication whether it should be called with parameters at all.

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 burden. It discloses a key behavioral trait: 'The body is discarded.' This tells the agent the tool is stateless (no persistence or side effects on the input), which is valuable information beyond the bare validation action. It could add more about whether it logs or errors, but the discard statement is already strong.

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 sentences, zero waste. The core purpose is first, followed by an important side-effect disclosure. 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?

The tool has no output schema, so the description should state what the validation returns (e.g., boolean, error code), but it does not. Furthermore, the 4-parameter schema includes three completely unrelated params and the description does not explain their role or how the tool interprets them, leaving an agent with unresolved confusion about a simple validator.

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

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

Despite 100% schema coverage, the schema contains three parameters (url, host, zone) that describe URL/host/timezone operations irrelevant to JSON validation, and one 'json' parameter that matches the tool's purpose. The description only says 'a body' and does not clarify whether url/host/zone are ignored, required, or apply to a different mode. This creates serious ambiguity for an agent trying to populate the request, so the description fails to add corrective 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 states a specific verb and resource: 'Check whether a body is valid JSON.' This clearly distinguishes it from the sibling tools, which are all URL/timezone operations (normalize-url, timezone, status), making its purpose 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 exact use case is obvious: use this tool when you need to verify if a JSON string/body is syntactically valid. Though it doesn't explicitly name alternatives, no sibling overlap exists, so the clear context is sufficient. It lacks an explicit 'when-not-to-use' statement, but the purpose is specific enough to make the guidance clear.

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