ISO 4217 currency shape

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

No annotations exist, so the description carries full responsibility. It mentions 'Returns connection methods' but does not clarify side effects, whether the tool is read-only, or what happens with inputs. The repeated 'discarded' hints at no mutation but is not a clear behavioral contract.

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, which is good, but it sacrifices clarity for brevity. The schema descriptions are also terse. The structure is acceptable, but the content is too vague to be effective.

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 9 heterogeneous parameters and no output schema, the description should explain what the tool actually does with these inputs. It fails to connect the parameters to a coherent behavior. The 'discarded' notes and the catch-all 'tool gateway' leave the agent without sufficient context to make a correct call.

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

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

The schema provides descriptions for all 9 parameters (100% coverage), giving some semantic meaning (e.g., 'HTTPS URL to normalize or cite'). However, the underlying tool description is ambiguous about how parameters are used, and many descriptions end with 'discarded,' which undermines their purpose. The baseline of 3 is maintained because descriptions exist but add limited clarity.

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 purpose ('Find a public pay-per-call tool gateway') but is vague and ambiguous. It mentions 'task such as weather, search, scrape, or voice' yet immediately says 'Task text discarded,' which contradicts the idea of task-based selection. It does not clearly distinguish from sibling tools like weather-hint or search-query-len.

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. The description lists example tasks but does not specify conditions, prerequisites, or comparisons to sibling tools. It leaves the agent guessing.

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 behavioral burden. It adds one useful disclosure — 'Page content is not stored' — but omits that the tool performs a network fetch, what happens when the URL fetch fails, and that json and zone parameters have their own behaviors. It does not contradict any annotations because none exist.

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

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

Two short sentences, with the primary result front-loaded. However, the brevity reflects under-specification rather than earned conciseness — the tool has four parameters spanning three domains, and only one is addressed. The second sentence adds a privacy note but raises unanswered questions about the other parameters.

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

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

For a 4-parameter tool with no annotations and no output schema, the description is incomplete. It doesn't describe the return format, the behavior of the json/zone/host parameters, error handling, or when each parameter should be used. The tool appears to be a multi-purpose utility, and the description covers only its URL-citation facet.

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 little. The description only reinforces the url parameter's semantics and says nothing about host, json, or zone beyond what the schema already states. Since the schema does the heavy lifting, no penalty beyond baseline is warranted.

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 concrete result — host, scheme, and HTTP status for a URL — which is clear on its face. However, the schema exposes four parameters spanning unrelated domains (url, host, json, zone), and the description only accounts for the URL aspect. It also does not distinguish this tool from the sibling normalize-url, leaving overlap 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?

No guidance is given on when to use this tool versus siblings like normalize-url, validate-json, or timezone. The description also fails to explain that the tool apparently handles JSON validation and timezone inputs, so an agent has no instruction on which parameters to supply for which task.

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 fully bears the behavioral disclosure burden. It does add one meaningful privacy detail—'No identifiers are retained'—but omits other behavioral traits such as side effects, persistence, rate limits, or return shape. This is minimal behavioral context.

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

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

The description is very short, front-loaded with the main action, and contains no filler. It earns good marks for conciseness, though the brevity borders on under-specification.

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 parameters with no required fields and no output schema, yet the description does not explain how those parameters relate to the classification or what the response will look like. An agent would be guessing about the tool's core 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 all four parameters ('url', 'host', 'json', 'zone') are already documented in the schema. The description itself adds no parameter-level meaning, which matches the baseline of 3.

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

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

The description says the tool shows how a request is classified, which identifies a verb and a resource at a high level. However, it never specifies what classification dimensions or labels are involved, and it does not distinguish this tool from its siblings such as 'citation', 'common', or 'country'.

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 sibling tools, nor when not to use it. The context of classifying a request is implied but not explicit enough to route an agent correctly among many similar-looking options.

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 transparency burden. It discloses that the operation is a read-only transformation (splitting) and that it does not fetch WHOIS/ownership data, which is useful. But it does not state side effects, permissions, output format, or how the other parameters are treated.

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 12-word sentence that immediately states the action and the key exclusion. It is well front-loaded and contains no filler, though it is arguably too sparse for a tool with four heterogeneous parameters.

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

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

Given the tool has four optional parameters covering URL normalization, JSON validation, and timezone handling, a one-sentence description of hostname splitting is incomplete. The description does not mention the output shape of the split (e.g., an array of labels), the role of the other parameters, or any fallback behavior. An agent would struggle to call this tool correctly for url, json, or zone inputs.

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; each parameter already has a meaningful schema description. The description adds the context that 'host' is the input to split, but it does not explain how url, json, or zone relate to the declared 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 uses a specific verb ('Split') and resource ('a hostname into labels'), and clarifies that it does not perform WHOIS or ownership lookups. This gives a clear operational purpose. However, it does not differentiate from any sibling (the only listed sibling is the tool itself) and does not account for the url/json/zone parameters in the schema.

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 is for hostname label splitting and explicitly excludes ownership/WHOIS data, so an agent knows it is not the right tool for domain registration lookups. It gives no positive when-to-use conditions, prerequisites, or alternatives, and the presence of unrelated parameters (url, json, zone) further obscures when to call it.

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

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

No annotations are provided, so the description must disclose behavior itself. It does not mention side effects, return format, whether inputs are validated or transformed, or why unrelated parameters like url and json appear in the schema. This is a substantial 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 undeniably terse, but under-specification for a 4-parameter tool is not good conciseness. There is no structure or front-loading of actionable information; it reads like a caption rather than a functional 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?

For a tool with 4 optional parameters, no output schema, and no annotations, a six-word phrase is far from complete. It does not explain how the timezone list relates to url/host/json, what results look like, or whether calling the tool has any effect, so an agent cannot reliably select or invoke it.

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

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

Schema description coverage is 100%, so each parameter (url, host, json, zone) already has a textual description in the schema. The tool description adds no parameter-level meaning and appears disconnected from those parameters, but the schema carries the burden, 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 reads as a noun phrase ('Common IANA timezone names for clock calls') rather than a tool behavior; it lacks a verb indicating what the tool does with those names. It adds a domain hint but mostly restates the tool name, so an agent cannot tell whether this is a lookup, validation, or citation tool.

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

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

There is no guidance on when to invoke this tool versus siblings like citation or compat, or when not to use it. The phrase 'for clock calls' weakly implies a use case, but no conditions, prerequisites, or alternative-selection cues 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, the description carries the full burden, but it fails to disclose critical behavior and actively conflicts with the input schema. The schema parameters ('normalize or cite', 'JSON validate', 'IANA timezone') have nothing to do with fetching robots.txt, so an agent cannot infer how the tool actually behaves.

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

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

The description is a single, front-loaded sentence with no filler. It is concise and readable, though the conciseness comes at the cost of missing essential 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 definition is severely incomplete for a tool with 4 parameters, no annotations, and no output schema. It does not explain how to specify the robots.txt URL, what 'group counts' means, or why the schema contains unrelated parameters, leaving an agent unable to invoke it correctly.

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

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

Although schema coverage is 100%, all four parameter descriptions are generic and unrelated to the tool's stated purpose. The 'url' parameter is described as 'HTTPS URL to normalize or cite' rather than the site whose robots.txt should be fetched, and 'json' and 'zone' have no connection to robots.txt at all. This makes the parameters misleading rather than meaningful.

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

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

The description uses a specific verb ('Fetch') and resource ('public robots.txt') and states the result ('return group counts only'). This makes the intended action clear in isolation, though it doesn't explicitly differentiate from sibling tools.

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 prerequisites, and no exclusions. The only hint is 'return group counts only,' which is a scoping constraint rather than usage direction.

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 none: no side effects, no return behavior, no prerequisites, no indication of whether this is a read-only or mutating operation. The phrase 'currency shape' hints at a structural check but provides no concrete behavioral detail.

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 contains no actionable verb, no tool behavior, and no parameter mapping, so it does not earn its place as a useful 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?

For a tool with four optional parameters, no output schema, no annotations, and many siblings, this description is far too incomplete to support correct selection or invocation. It leaves every meaningful question about the tool's behavior and inputs unanswered.

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 nothing about parameters. However, the description also fails to explain how 'ISO 4217 currency shape' relates to url, host, json, or zone, making the parameter list appear disconnected from the tool's apparent 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 'ISO 4217 currency shape' is a noun phrase with no verb, so it never states what the tool does. It does not say whether it validates currency codes, returns a data shape, or performs some other operation. The name suggests a validation/OK check, but the description does not confirm this, and the unrelated parameters (url, host, json, zone) add further confusion.

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

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

There is no guidance about when to use this tool versus any sibling tool. It does not mention alternatives, exclusions, or conditions under which an agent should select it. Without this, an agent has no way to route between iso4217-ok, validate-json, domain-shape, or normalize-url.

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

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

With no annotations, the description carries the burden of disclosing behavior. It does disclose that query and fragment are dropped, which is a meaningful behavioral trait. However, it does not mention what happens with invalid URLs, whether HTTPS is enforced, or that the schema's host/json/zone parameters appear unrelated to this tool's 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?

Two sentences with no filler. The main behavior is front-loaded and the key exception (dropping query/fragment) follows immediately. 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?

For a tool with four schema parameters, no annotations, and no output schema, the description is too thin. It does not specify the return shape (object vs. string), clarify which parameters apply, or address edge cases. The presence of unrelated parameters in the schema makes this incompleteness more harmful.

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%, but the description only adds meaning for the url parameter. The remaining three parameters (host, json, zone) are present in the schema and described for other purposes, creating real ambiguity about whether they can or should be passed to normalize-url. The description does not clarify that only url is relevant.

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 ('Return') and names the resource (a URL) along with exactly what is returned (origin, host, path) and what is dropped (query, fragment). This is clear and actionable, though it does not explicitly differentiate from sibling tools like validate-json or host-to-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?

No guidance is given about when to use this tool versus alternatives, nor are any exclusions or prerequisites stated. The intended context ('need origin/host/path') is only implied by the behavior, not 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 provided, the description carries the full burden of behavioral disclosure, and it discloses almost nothing: no indication of what the catalog returns, whether inputs filter or look up entries, or whether the operation is read-only. The schema's parameter descriptions ('JSON text to validate; discarded after the check') imply behaviors that contradict the description's stated purpose of an HTTP status-code catalog, leaving an internally inconsistent picture.

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 contains no filler and is front-loaded with the core topic, which is efficient. But it is a fragment that under-specifies a 4-parameter, zero-annotation tool — brevity is achieved at the direct expense of the detail this tool needed, so it is barely minimally appropriate in size.

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 annotations and no output schema, the description must carry the explanatory load, and the one-line noun phrase covers nearly none of it: expected return value, how the four parameters map to the catalog, side effects, and sibling differentiation are all absent. An agent cannot reliably determine how to invoke this tool correctly from the information provided.

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

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

Schema coverage is 100%, so the baseline is 3: each parameter has a clear one-line description that conveys its literal meaning. However, the tool description adds no parameter semantics at all, and the schema's parameter descriptions appear to be lifted from sibling tools rather than tied to a catalog of HTTP status codes, creating cohesion confusion about why these inputs exist together.

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 verbless noun phrase — 'Short catalog of common HTTP status codes' — that essentially restates the tool name 'status-catalog' and never states an operation the agent can invoke. Worse, the stated purpose (HTTP status codes) has no visible connection to the four parameters (url, host, json, zone), so an agent reading the description cannot tell what calling this tool actually does. It also fails to differentiate the tool from its siblings, whose parameters it appears to borrow.

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 offers no guidance on when to use this tool, no exclusions, and no mention of alternatives such as url-normalizer, validate-json, or timezone — even though the parameters plainly overlap with those sibling tools. An agent deciding between status-catalog and a sibling when given a URL or JSON input gets no help resolving the ambiguity.

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 states the output ('current time') without mentioning what happens for invalid zones, whether any network/state effects occur, or what the return format is. This is minimal transparency 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?

The description is a single, front-loaded sentence with no filler. It efficiently communicates the core behavior without wasting tokens.

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 not complete enough given the mismatched schema: the presence of url, host, and json parameters strongly confuses the tool's actual purpose, and there is no output schema or annotations to compensate. An agent cannot confidently infer how to invoke this tool correctly beyond guessing at 'zone'.

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

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

Although schema coverage is 100%, the schema contains three unrelated parameters (url, host, json) that do not match the described timezone functionality. The description does not clarify that only 'zone' is relevant, creating significant ambiguity about which parameter actually drives the tool.

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 returns the current time for a named IANA timezone, which is a specific and recognizable purpose. It also implies differentiation from sibling tools like utc by emphasizing 'named IANA timezone', though it does not explicitly name the alternative.

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 this tool should be used when a specific named IANA timezone is available, rather than a general UTC time. However, it gives no explicit when-to-use or when-not-to-use guidance and does not reference any sibling tool as an alternative.

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 and a description that only restates the name, the description fails to disclose any behavioral traits: whether the tool performs network calls, validates input, normalizes data, or simply returns the current time. The presence of a 'json' parameter described as 'discarded after the check' suggests validation behavior, but the description doesn't mention it. This is a severe lack of transparency for a tool with such a misleading name.

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, which is normally a positive trait for conciseness, but here it is under-specification rather than concise efficiency. 'Current UTC timestamp' is a single fragment that cannot be considered a well-structured description. It earns the low end because it wastes the reader's time by providing no actionable information beyond the name.

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

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

Given the complexity of a tool with four unrelated parameters, no required fields, no output schema, and no annotations, the description is severely incomplete. An agent cannot determine what the input parameters do, which are needed for the intended use case, what the return value looks like, or how this tool relates to sibling tools like 'citation' or 'domain-shape'. The definition fails at every level of contextual completeness.

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 the schema has 100% description coverage for each parameter, the description contributes nothing to parameter semantics. The tool is named 'utc-time', yet its schema includes four unrelated parameters (url, host, json, zone) with descriptions that do not connect to time retrieval. The descriptions say 'HTTPS URL to normalize or cite', 'Public hostname', 'JSON text to validate', and 'IANA timezone name'—none clarify how these relate to obtaining a UTC timestamp. The schema may document each parameter individually, but the tool-level meaning is completely absent.

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 a tautology—it restates the tool name without specifying what action the tool performs, what input it expects, or what output it produces. The input schema contains four unrelated parameters (url, host, json, zone), none of which are marked required, creating a glaring mismatch between the description and the actual invocation interface. An agent cannot determine what this tool does with any of these parameters.

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 zero guidance on when to use this tool or how it differs from siblings like 'citation' or 'compatibility'. There is no mention of which parameters are relevant for obtaining the UTC timestamp, nor any exclusion criteria. The agent is left to guess whether all four unrelated parameters are needed, optional, or ignored.

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?

It discloses one meaningful behavioral trait: the body is discarded after validation, which is useful since no retention is implied. But with no annotations and no output schema, it does not say what the tool returns on valid/invalid JSON or how failures are signaled, leaving the main outcome under-specified.

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

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

Two short sentences with no filler; the purpose is front-loaded and the side effect follows immediately. 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 description is not complete enough given no annotations and no output schema. It does not explain which of the four optional params carries the JSON to validate, what a successful or failed validation returns, and why url/host/zone are part of this tool. Schema descriptions help but cannot compensate for the missing tool-level semantics.

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?

All four parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description adds no mapping or clarification; specifically it does not state that the json parameter is the body to validate or explain why url, host, and zone are accepted.

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?

States a concrete action ('Check whether a body is valid JSON') and a clear side effect ('discarded'). However, it never ties the 'body' to the json parameter, and with unrelated parameters such as url/host/zone present the target input is ambiguous, so it doesn't fully distinguish itself beyond the name.

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

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

No guidance on when to call this tool relative to siblings like iso4217-ok or status-catalog; no explicit when-to-use or when-not-to-use conditions. The expected input scenario (having a JSON text to validate) is only implied by the tool's name and the json parameter description.

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