ISO week number

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 discloses that page content is not stored, which is useful, but omits network behavior, error handling, rate limits, or side effects (e.g., whether the URL is fetched server-side). For a tool that validates URLs, this is thin.

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 with the core behavior and a key limitation. It earns its place with no filler, though it ends abruptly and does not enumerate parameter roles.

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 schema defines four parameters but the description explains only one behavior (returning host/scheme/status). With no output schema and no annotations, the agent lacks context for what happens with json or zone, what the output format is, or when this tool is preferable to the many sibling tools. This is under-specified for a tool with four optional parameters.

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 the schema already describes each parameter individually (url, host, json, zone). The description adds no parameter-specific detail beyond 'host and scheme' for the URL. The presence of open parameters with no required fields and no functional description beyond the schema leaves the agent to rely on schema alone, so baseline 3 is appropriate.

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–resource pair ('Return host, scheme, and HTTP status for a URL') and adds one distinguishing fact ('Page content is not stored'). However, it does not mention other input fields (json, zone) or sibling tools, so the tool's broader purpose is only partially conveyed.

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

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

The description gives no explicit guidance on when to use this tool versus alternatives, and the sibling list includes many similarly named tools (normalize-url, validate-json, etc.) with no routing hints. The only contextual clue is the negative statement about page content not being stored, which weakly implies a lightweight citation-checking 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 provided, the description carries the full burden. It does disclose a meaningful behavioral trait—'No identifiers are retained'—and 'Show' weakly implies a read-only operation. However, it does not state whether any data is stored, what output the classification produces, or whether there are side effects, leaving significant behavioral ambiguity.

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

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

The description is two short sentences with no filler, and the primary purpose is front-loaded. It earns its conciseness, though it is borderline under-specified rather than simply compact.

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 has four optional parameters and no annotations or output schema, the description is notably incomplete. It does not explain what classifications are possible, how the output should be interpreted, or how this tool differs from its siblings, leaving an agent under-equipped to invoke it meaningfully.

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 (url, host, json, zone) are already documented in the schema. The description adds no extra meaning about how these parameters relate to the classification, so the baseline score of 3 is appropriate.

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: 'Show how this request is classified.' This is clear enough to establish an action and object, and 'No identifiers are retained' adds a defining trait. However, it does not differentiate this from siblings like normalize or validate_json, and 'classified' remains somewhat abstract without naming the classification scheme.

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

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

The description gives no guidance on when to use this tool versus alternatives such as citation, domain-shape, normalize, or validate_json. The privacy note 'No identifiers are retained' implies a privacy-sensitive context, but this is not explicit and no when-to-use or when-not-to-use conditions are stated.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose a key negative trait (no WHOIS/ownership data), but it omits other behaviors suggested by the schema, such as JSON validation and discarding the input after the check. The description is too narrow relative to the actual parameter surface.

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 economical sentence with the core action front-loaded and a useful exclusion appended. It contains no fluff, though it errs on the side of being too terse to fully inform the agent.

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

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

With four optional parameters, no output schema, and no annotations, the description is too sparse. It does not explain the return format, how the parameters interact, or when this tool is appropriate. An agent would struggle to invoke it correctly in an unfamiliar 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 schema already documents each parameter. The description adds no parameter-level meaning and does not clarify how url, json, or zone relate to splitting a hostname. Baseline 3 is appropriate.

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'. The qualifier 'without WHOIS or ownership data' usefully differentiates it from ownership-related tools. However, the presence of url, json, and zone parameters in the schema is not explained, so the full purpose remains somewhat ambiguous.

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. There are no use-case scenarios, exclusions, or references to sibling tools. An agent gets only the action, not the decision 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 offers almost none: no return shape, no side effects, no filtering semantics, and no indication of what happens with the url, host, or json inputs. The phrase 'for clock calls' hints at a use case but does not describe tool 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 text is short, but brevity is not the same as good structure. One short clause is easy to parse, yet it omits the core operation and fails to earn its place as a usable tool definition.

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

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

With four heterogeneous parameters, no output schema, and no annotations, a one-clause domain statement is far from sufficient. An agent cannot infer how the parameters relate, what inputs are required, or what the response will look 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 each parameter has a documented meaning. The description adds no parameter-specific value; the 'zone' property aligns loosely with the description, but url, host, and json are entirely unaddressed 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 is a noun phrase that mostly restates the tool name: 'Common IANA timezone names' is essentially another way of saying 'iana-zones'. It adds no verb or action, so an agent cannot tell whether this tool lists zones, validates them, or returns a reference list.

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

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

There is no guidance on when to use this tool versus its siblings, which appear to include normalize, cite, validate, and time. The description does not explain which input should be used for which scenario or when this tool is preferred over 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?

There are no annotations, so the description carries the full burden. It discloses that only group counts are returned and that the input is public, implying no authentication needed. However, it is silent on how invalid URLs, non-existent robots.txt, redirects, or date/download limitations behave, so an agent may be uncertain about edge cases.

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 efficient sentence with no filler. It front-loads the action, resource, and output format while keeping the description extremely small.

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 no output schema and no annotations, the description is adequate for a simple fetch tool. However, it does not clarify which URL formats are acceptable (e.g., must include http/https), what happens if robots.txt is absent, or why 'json' and 'zone' parameters are accepted, leaving some ambiguity about behavior.

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

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

Schema description coverage is 100%, so the schema already documents each parameter (url, host, json, zone). The description itself adds no further meaning beyond 'public robots.txt', so the schema does the heavy lifting here.

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

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

The description states a specific verb ('fetch') with a resource ('public robots.txt') and a clear scope ('return group counts only'). It distinguishes the tool's simplified purpose from a full-fetch or parse tool, though it does not explicitly name sibling alternatives.

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

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

The description implies usage: use this when you only need group counts from a robots.txt, not the full file. It doesn't explicitly state when not to use it or recommend alternatives, but the 'group counts only' phrasing gives reasonable 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?

With no annotations present, the description carries the full burden of behavioral disclosure, and it completely fails to do so. It says nothing about what inputs are consumed, whether the operation is read-only, what the return value looks like, or how the four unrelated parameters (url, host, json, zone) relate to an ISO week calculation.

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. Three words do not earn their place because they convey no operational information beyond the tool 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?

For a tool with four optional parameters, no output schema, no annotations, and ten siblings, the description is grossly incomplete. An agent cannot determine what input to provide, what result to expect, or how this tool differs from related time and validation tools.

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

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

Schema description coverage is 100%, so the baseline is 3 even though the description itself adds no parameter-level meaning. However, the schema descriptions are generic and do not explain how url, host, json, or zone relate to ISO week numbers, so the description provides no additional semantic value.

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

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

The description 'ISO week number' is essentially a tautology of the tool name 'iso-week' and does not state an operation, verb, or resource. It gives no indication of whether the tool computes, validates, or converts ISO week numbers, and it does not distinguish the tool from siblings like timezone or utc-time.

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 for when to use this tool versus alternatives. The description does not mention any context, prerequisites, exclusions, or relationships to sibling tools such as timezone, utc-time, 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?

The description does disclose that query and fragment are dropped, which is useful behavioral transparency. But with no annotations available, the description carries the full burden and fails to mention what happens with invalid URLs, whether any network request is made, or what behavior is expected when 'json' or 'zone' are supplied. The behavioral scope of the tool is only partially disclosed.

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 concise and front-loaded: two sentences that state the core behavior directly without redundant wording. It is appropriately sized for the URL normalization aspect, though it omits other functionality.

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 parameters, no annotations, and no output schema, so the description should supply enough context for correct invocation. It provides contextual detail only for the 'url' parameter, leaving the purposes and behaviors for 'host', 'json', and 'zone' unexplained. The schema's parameter descriptions help but do not compensate for the missing overall tool contract.

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

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

Schema description coverage is 100%, so each parameter has its own description in the schema. The main description adds little beyond that except for clarifying the output focus on origin, host, and path. It does not explain the relationship between the parameters or how 'host', 'json', and 'zone' relate to URL normalization.

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 ('Return') and resource (URL), and clearly explains the normalization behavior ('Query and fragment are dropped'), which distinguishes it from sibling tools. However, it only covers the 'url' parameter, while the schema also includes unrelated parameters 'host', 'json', and 'zone' that the description does not account for. An agent cannot determine the tool's full scope from this description.

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, and the description does not mention any of the sibling tools like validate-json or timezone-related tools. It also does not explain how the 'host', 'json', or 'zone' parameters should be used if they are provided, 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?

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'catalog', which suggests a read-only reference without detailing any side effects, input/output behavior, or special constraints. It doesn't disclose what the tool does with the provided URL, host, json, or zone parameters, or what the return value looks like. This is a significant gap for a tool that accepts a heterogeneous set of parameters.

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

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

The description is a single, short sentence with no filler words. It is appropriately sized for a simple reference tool, though it could add a bit more actionable detail without becoming bloated.

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 odd mix of parameters (url, host, json, zone) with no required params and no output schema, the description is far from complete. An agent cannot determine what the tool does with these inputs, what it returns, or how it relates to a catalog of HTTP status codes. The description is inadequate for the tool's complexity and ambiguous parameter design.

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% coverage for the four parameters, with each having a basic description ('HTTPS URL to normalize or cite', 'Public hostname', 'JSON text to validate; discarded after the check', 'IANA timezone name'). However, the description does not explain why these parameters relate to a catalog of HTTP status codes, and the connection is unclear. Baseline 3 is appropriate because the schema carries the parameter documentation, but the description adds little semantic cohesion.

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' gives a specific subject (HTTP status codes) and indicates it is a catalog/reference, which is reasonably clear. However, it doesn't state the tool's actual behavior—whether it returns codes, maps them, or validates them—so it lacks a strong action verb. It partially distinguishes itself from siblings like 'citation' or 'compatibility' but not explicitly.

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 the sibling tools such as 'citation', 'compatibility', or 'validate-json'. The description only says it is a catalog of status codes, leaving the agent to infer when this is relevant. No explicit when-to-use or alternatives 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?

With no annotations provided, the description carries the burden of behavioral disclosure. 'Current time' strongly implies a non-mutating read operation, and the lack of side effects is reasonably inferable for such a simple lookup. But it does not disclose the output format, any error behavior for invalid zone names, or whether the operation performs network requests.

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, tight, front-loaded sentence with zero wasted words. Every word earns its place and the core purpose is immediately visible.

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 parameters, none required, and the description only references one of them. It does not clarify that `url`, `host`, and `json` are irrelevant to this tool's operation or what the return value looks like, leaving an agent uncertain about how to actually 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?

Schema description coverage is 100%, so the schema already documents all four parameters, and the description adds no meaning beyond what the schema states. The only relevant parameter, `zone`, is already described as an 'IANA timezone name' in the schema; the description merely rephrases that.

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 phrase ('Current time') plus a precise resource ('named IANA timezone'), making it instantly clear what the tool does. It maps directly to the singular `zone` parameter and is distinguishable from sibling tools like normalize-url and validate-json without any 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 wording implies the tool is for looking up the current time in an IANA zone, which is a clear enough use case. However, it gives no explicit guidance about when not to use it or which sibling alternatives might be relevant, leaving usage decisions mostly 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?

With no annotations provided, the description carries the full burden of behavioral disclosure, and a one-line statement reveals almost nothing: no return format (ISO string, epoch seconds, milliseconds), no statement about side effects, and no acknowledgment of the four schema parameters that appear unrelated to the described purpose. The mismatch between the single-purpose description and the multi-parameter schema is unexplained and potentially misleading.

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

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

The description is maximally concise at four words, and the single sentence carries no waste. However, conciseness crosses into under-specification given the four-parameter schema and the need to differentiate from eight sibling tools; more explanatory content is warranted, so the brevity is not fully appropriate to the tool's complexity.

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, no annotations, and only a minimal description. Given the four unrelated-looking optional parameters, an agent cannot confidently determine invocation details, return value shape, or how this tool differs from the 'timezone' sibling. The definition is incomplete for reliable selection and correct calling.

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 description adds zero parameter semantics and does not mention any of the four parameters. Worse, the parameters themselves (url, host, json, zone) describe behaviors foreign to 'Current UTC timestamp', so an agent cannot tell whether any of them should be supplied or are simply ignored. The description fails to reconcile or explain the parameter surface.

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 the tool's output: the present UTC time. It is unambiguous about what the tool returns and is distinguishable in intent from the sibling 'timezone', though it does not explicitly name that alternative. However, the description is terse and the attached schema lists four unrelated parameters (url, host, json, zone), which muddies the agent's picture of what this 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?

The description implies the tool should be used when the current UTC time is needed, but it provides no explicit when-to-use guidance and no differentiation from siblings such as 'timezone' or 'iso-week'. There are no exclusions, prerequisites, or alternative routing given, leaving an agent to infer selection criteria entirely from the tool name.

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?

Even with no annotations to rely on, the description discloses a meaningful behavioral trait—that the input body is discarded after the check—which is valuable for an agent to know before invoking the tool. It does not explicitly state side effects, but the discard statement effectively communicates the non-persistent nature of the operation.

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 concise and well-structured: two short sentences that front-load the core purpose and then add the key behavioral detail. There is no filler or repetitive content.

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

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

The description plus the fully covered schema is adequate for a simple validation tool, but the absence of an output schema means the description should have clarified what is returned (e.g., a boolean, an error, or a status code). Given zero annotations, this is a meaningful gap, though not severe.

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 all four parameters are already documented in the input schema. The description adds important semantic context for the 'json' parameter by stating that it is 'discarded after the check', which clarifies its lifetime and purpose beyond the schema's generic 'JSON text to validate'.

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 the specific verb phrase 'Check whether a body is valid JSON' to establish the tool's purpose as a validation operation, and explicitly states 'The body is discarded' to clarify its side-effect scope. It is well-differentiated from the sibling tools, which are oriented toward URL/host/timezone normalization and citation, though it doesn't name 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?

The description implies a straightforward, one-shot validation use case, but provides no explicit 'when to use' guidance or exclusion cues. It does not reference alternatives or warn against misuse, leaving some judgment to the agent.

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