Asia/Shanghai clock

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

With no annotations, the description carries the full burden and does add one useful disclosure: "Page content is not stored." But it stops there — it does not say whether the tool performs network fetches, follows redirects, handles unreachable URLs, or whether the json/zone branches have side effects. Partial disclosure, no contradiction.

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, each earning its place: one states the purpose, the other a behavioral claim. The key output is front-loaded with no filler.

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

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

For a four-parameter, zero-required tool with no output schema and no annotations, the description covers only the URL case. It does not explain return shape, parameter combination rules, error behavior, or alternatives among params. The schema descriptions help but cannot carry the missing 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 meaning for 'url' by specifying its outputs, but it never relates host, json, or zone to any behavior, and it is ambiguous whether 'host' is an input or the returned host. The schema descriptions are minimal, so the tool's multiple modes remain 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 states a specific output for one use case: "Return host, scheme, and HTTP status for a URL." However, the input schema carries three additional parameters (host, json, zone) whose purpose the description never acknowledges, so the stated purpose does not describe the whole tool. It also does not differentiate from sibling tools such as normalize-url, status-catalog, validate-json, or timezone.

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

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

No guidance is given on when to use this tool vs. its siblings. The description offers neither exclusions nor alternatives, and the sibling set overlaps heavily with the JSON and timezone parameters, leaving an agent to guess which tool handles what.

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

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses one meaningful trait — 'No identifiers are retained' — but does not state whether this is a read-only operation, what the classification output looks like, how errors are handled, or whether data is sent elsewhere.

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 with no padding; the privacy statement is a distinct, useful addition. Brevity is a virtue here, even though it sacrifices explanatory substance.

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

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

The tool accepts four heterogeneous optional inputs and has no output schema or annotations, so the description needs to explain how each input is classified and what the result will be. It does not, leaving an agent guessing about the return format and the meaning of 'classified.'

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 that url, host, json, and zone are accepted, giving a baseline of 3. The description adds no relationship between these parameters and the classification behavior, leaving it unclear whether they are alternatives or must be combined.

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

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

The description uses a specific verb ('Show') and identifies the resource ('how this request is classified'), but the term 'classified' is vague — it doesn't say what kind of classification (validity, compatibility, safety, etc.) or what categories result. It also doesn't distinguish the tool from siblings like validate or normalize, leaving selection uncertain.

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 when-to-use guidance or mention of alternatives is provided. With siblings such as validate, normalize, and citation present, an agent has no basis for choosing compatibility over them. The privacy note hints at a context, but it doesn't clarify when this tool should be preferred.

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 usefully states that the tool does not perform WHOIS or ownership enrichment, which sets an important boundary. However, it says nothing about side effects, return format, or how edge cases (invalid hostnames, URLs, JSON, timezone inputs) are 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, straightforward sentence. It front-loads the primary action and the notable limitation (no WHOIS/ownership) with zero wasted words.

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

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

Given four parameters, no output schema, and no annotations, the description is too thin. It does not explain how the various input fields should be supplied or what the tool returns, and the connection between 'split a hostname' and the 'json'/'zone' parameters is unclear. An agent would need to inspect the schema and guess at the intended use.

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

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

Schema description coverage is 100%, so each parameter already has a baseline definition. The tool description adds no additional meaning about how 'url', 'host', 'json', and 'zone' relate to splitting a hostname into labels, leaving their roles somewhat disconnected from 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 clearly states a specific action ('Split a hostname into labels') and explicitly excludes WHOIS/ownership data, making the tool's core purpose unambiguous. It does not name sibling tools or mention how it relates to them, which prevents a perfect score.

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. The phrase 'without WHOIS or ownership data' implies it is not a WHOIS lookup tool, but no explicit conditions or alternative tool names are provided, leaving the agent to infer usage 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 reveals nothing about return values, side effects, required inputs, or failure modes, and it does not account for the four parameters in the schema, which include url, host, and json that seem disconnected from 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 only one short sentence with no filler, but it is under-specified rather than efficiently complete. It lacks a verb and any structural detail, making it too thin to be considered a well-structured description.

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 output schema, and no annotations, this description is far from complete. It gives a vague domain hint but fails to explain what the tool does, what it returns, or how the parameters relate to the declared 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 the baseline is 3 even though the description adds no parameter-level meaning. The description does not clarify how zone, url, host, or json should be used, and it fails to explain why url, host, and json are relevant to IANA timezone names.

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 subject matter (common IANA timezone names) and an intended context (clock calls), but it is a noun phrase rather than an explicit verb+resource statement. An agent cannot tell whether invoking this tool returns a list, filters names, or does something else.

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 instead of siblings like utc-time, validate-json, or normalize-url. The phrase 'for clock calls' hints at a use case, but it does not state conditions, exclusions, or alternatives.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state that fetching a public URL might fail, that the tool only counts groups and does not return the full content, what happens on redirects or network errors, or whether the tool is a read-only operation. The word 'Fetch' implies a network read, but nothing clarifies the tool's behavior beyond the bare action. The biggest gap: the tool accepts a JSON parameter, a zone parameter, and a host parameter that seem irrelevant to fetching robots.txt, and the description does not explain what happens to them.

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 sentence, no filler, front-loaded with the verb and resource. However, the single sentence is too terse to do its job — it states the minimum verb phrase without context that would justify its length. Concise but not complete.

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?

This tool has 4 parameters, no annotations, and no output schema. The description must compensate for all of that, and it does not. It does not say what the output looks like, which parameters matter, how to handle failures, or when to prefer it over a sibling. For a network operation with multiple unrelated-looking parameters, this is 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?

Schema description coverage is 100%, but the description adds zero value for parameters. The parameter descriptions themselves are weak ('HTTPS URL to normalize or cite', 'Public hostname', 'JSON text to validate; discarded after the check', 'IANA timezone name') and the tool description does not clarify which parameters are actually relevant for fetching robots.txt or how they interact. For a network fetch tool, the description should at least map the parameters to their role in the fetch. It does not.

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 'Fetch a public robots.txt and return group counts only.' It uses a specific verb and resource, but the title 'inspect-robots' is nearly identical in meaning, so the description adds little beyond the name. It also does not distinguish this tool from its siblings or clarify what 'groups' means (user-agent groups? crawl-delay groups?), leaving 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?

There is no guidance on when to use this tool versus alternatives, no scenarios, no exclusions, and no mention of what not to use it for. The description simply states the action with no context for an AI agent to decide if this is the right tool. With no annotations and no sibling differentiation, the agent must 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 does disclose the key behavior of dropping query and fragment, but it fails to explain how the 'host', 'json', and 'zone' parameters interact with URL normalization, and it says nothing about invalid URL handling or error 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 two short sentences with no wasted words, and the most important behavioral information is front-loaded. Both sentences earn their 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 description is incomplete for a tool with four heterogeneous parameters and no output schema or annotations. It is silent on how the non-URL parameters affect behavior, what the return format looks like, and what happens on errors or invalid input.

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 descriptions cover all four parameters, so the baseline is 3. The description adds meaningful context only for the 'url' parameter by noting query and fragment are dropped; it does not add any semantic value for 'host', 'json', or 'zone' beyond what the schema already states.

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 ('origin, host, and path for a URL'), and clarifies that query and fragment are dropped. This clearly distinguishes it from sibling tools focused on different resources, such as domain or validate-json.

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 intended use is implied by the name and the URL-focus of the description, but there is no explicit guidance on when to use this tool over siblings, nor any mention of alternatives or exclusions. The description relies entirely on 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, the description carries full responsibility for behavioral disclosure. It only states what the catalog contains, not what the tool does when invoked. There is no mention of output shape, lookup behavior, side effects, or how the provided parameters affect execution.

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

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

The description is short, but it is under-specified rather than appropriately concise. It repeats the tool name instead of earning its place with actionable information. There is no structure or front-loading of key behavioral details.

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

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

The tool has no output schema and no annotations, but the description does not explain what result to expect or how the four unrelated parameters are used. An agent cannot tell whether this is a read-only lookup, a static list, or something requiring the provided inputs, making the definition wholly inadequate for reliable 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%, and each parameter already has a self-contained description (url, host, json, zone), so the schema carries the parameter documentation. However, the description adds no bridge between these parameters and the stated catalog of HTTP status codes, leaving their role 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 is a noun phrase, 'Short catalog of common HTTP status codes,' which largely restates the tool name 'status-catalog' and lacks an action verb. It does not specify whether the tool returns a list of all codes, looks up a specific code, or does something else. It offers only the vague qualifiers 'short' and 'common.'

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 indication of when to use this tool versus any sibling. Worse, the input schema exposes unrelated parameters (url, host, json, zone) with no explanation of how they connect to HTTP status codes, which is misleading for an agent trying to select the right tool.

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

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It states a time is returned but does not describe the format (UTC, local, offset) or behavior for invalid or unknown zone names. It also silently ignores three of the four schema parameters, making 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?

A single, front-loaded sentence with no filler or repetition. It is as concise as a one-line tool description should be, even though the brevity leaves the schema mismatch unresolved.

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

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

With no annotations, no output schema, and a schema containing three unrelated parameters, the description is insufficient for correct invocation. An agent cannot tell whether url, host, and json are supported input forms, which parameter is required for a simple time lookup, or what shape the response takes.

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 description. The description reinforces that zone is an IANA name, matching the schema, but adds nothing about how url, host, or json relate to the tool; with 4 params and 0 required, the agent still cannot infer which is the intended input.

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

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

The description states a specific verb and resource ('Current time' + 'named IANA timezone') and clearly identifies the core function. It is easily distinguished from sibling tools like normalize, validate, and citation. However, it is ambiguous against the input schema, which also lists url, host, and json parameters that do not fit the stated purpose.

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

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

No usage guidance is provided. The description does not say when to use this tool, which parameter selects the zone, whether url/host/json are irrelevant or alternate input modes, or when a sibling tool would be more appropriate.

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 must carry the full behavioral burden. It states the primary read-only behavior, but it does not disclose that the tool appears to ignore the four provided parameters or clarify how the input schema relates to this fixed-timezone tool. No output format or edge-case behavior is described.

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. It is appropriately sized for what appears to be a simple time-lookup tool, and the key information is front-loaded.

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

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

The description is insufficiently complete given the confusing input schema and lack of output schema. It does not explain that the zone is fixed, that parameters are unnecessary, or what the returned time looks like. An agent invoking this tool may be uncertain whether to supply arguments or how to interpret the result.

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

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

Although schema description coverage is 100%, the parameters (url, host, json, zone) are unrelated to a fixed timezone tool and the description adds no clarification. An agent could easily be misled into passing a zone parameter or other unrelated arguments. The description should state that no parameters are meaningful or that they are ignored.

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

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

The description states a specific verb and resource: "Current local time in Asia/Shanghai." It clearly identifies what the tool returns and is distinct from sibling tools like utc-time or timezone by fixing the zone.

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 utc-time, timezone, or iana-zones. There is no mention of context, exclusions, or when the dedicated Asia/Shanghai tool is preferred.

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 present, so the description carries the full burden of behavioral disclosure. It states only that the output is a current UTC timestamp but does not specify the format (e.g., ISO 8601 string vs. Unix epoch), time precision, or whether the tool ignores the provided parameters. For a tool with zero annotation coverage, this is a significant 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 extremely concise — a single three-word sentence that is fully front-loaded. However, the brevity crosses into under-specification, leaving critical operational details unstated. It earns credit for leanness but sacrifices necessary structure and 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?

For a simple tool the core purpose is stated, but the description is incomplete in context: it doesn't mention that no parameters are required, it doesn't address the mismatch between the schema parameters and the tool's function, and there is no output schema to explain the return value. The description should at minimum clarify that parameters are optional/ignored or state the output format.

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

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

While schema description coverage is 100%, the parameters (url, host, json, zone) are clearly unrelated to retrieving a UTC timestamp, creating confusion. The description adds no meaning to these parameters and fails to clarify whether they are ignored, optional inputs, or artifacts of a copied schema. An agent cannot determine how to use the parameters correctly.

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 identifies the tool as returning the current UTC time with a simple predicate and resource ('Current UTC timestamp'). It does not explicitly distinguish itself from sibling tools like timezone or tz-asia-shanghai, but the resource ('UTC timestamp') is specific enough to convey the basic function.

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 timezone-related siblings, nor does it clarify how the four optional schema parameters (url, host, json, zone) relate to the tool's purpose. An agent cannot tell from the description whether passing a parameter like 'zone' is meaningful, ignored, or an error.

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 must carry the burden of behavioral disclosure. It states 'The body is discarded,' which is a side-effect note, but this exact information already appears in the schema description for the 'json' parameter ('discarded after the check'). The description adds no new behavioral insight (e.g., return value, error handling, or side effects beyond discarding). Thus, it merely repeats structured data without enriching agent understanding.

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 fluff. The primary purpose is front-loaded in the first sentence, and the second sentence delivers a concise behavioral note. Every word earns its place, making it efficient and easy to parse.

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

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

The description is incomplete for an agent. It does not explain what the tool returns (e.g., boolean, success/failure, or error), which is critical since there is no output schema. It also does not clarify the purpose of the other three parameters (url, host, zone) or whether they are ignored, leading to confusion about how the tool should be invoked. For a tool with multiple parameters and no annotations, this is a significant gap.

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%—every parameter (url, host, json, zone) has a description. The tool description does not add any parameter-specific meaning; it only refers to 'a body' which maps to the 'json' parameter but without clarifying the roles of the other three parameters. Per the rubric, high schema coverage sets a baseline of 3, and the description neither improves nor detracts from it.

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

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

The description clearly states the tool's function: 'Check whether a body is valid JSON.' It uses a specific verb ('check') and resource ('body' as JSON). It is distinct from all sibling tools, which deal with citations, domains, timezones, etc., leaving no ambiguity about what this tool 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 explicit guidance on when to use this tool versus alternatives. While the purpose is obvious, the description does not provide context like 'Use when you need to verify JSON format before processing' or mention any prerequisites. It neither states exclusions nor names alternative tools. The only usage hint is implicit via the purpose, which is not enough for a robust selection.

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