Common zone count

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

With no annotations, the description carries the burden. It discloses that task text is discarded, that path involves no disk access, and that several parameters are discarded after checks. However, it does not disclose authentication, rate limits, error behavior, or what happens if no gateway is found. It gives some transparency but is not comprehensive for a tool with no annotation support.

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 main description is two sentences: the purpose is front-loaded, the return type is stated, and the critical 'Task text discarded' warning is included. There is no filler; it is appropriately concise.

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 9 optional parameters and no output schema, the description is inadequate. It does not explain how to select which parameters to provide for a given task, what the returned 'connection methods' look like, or provide examples. An agent is left uncertain about how to map a user request to the correct parameter set and what to expect back.

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. The description adds significant value by explaining that most parameter values are only used for validation or shape checks and are discarded, and for path explicitly notes 'no disk access'. This clarifies the intent of each parameter beyond the schema, aiding correct usage.

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 ('Find') and resource ('public pay-per-call tool gateway') for tasks like weather, search, scrape, or voice, and mentions it returns connection methods. It is clear, but does not explicitly distinguish it from sibling tools, which are numerous and could overlap (e.g., weather-hint, 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?

The description implies usage for tasks such as weather, search, scrape, or voice, but provides no explicit when-to-use versus alternatives, no exclusions, and no mention of sibling tools. An agent must infer when this tool is appropriate instead of a more specific sibling.

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 adds a useful behavioral disclosure: 'Page content is not stored,' which reassures about non-persistence. However, it fails to disclose behavior when the json or zone parameters are passed, and does not mention that HTTP status implies a network fetch or any rate-limiting/caching aspects.

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 action front-loaded and a useful caveat. There is zero fluff or filler. It loses one point because, given the four-parameter schema, a sentence clarifying the multi-purpose nature would have been more valuable than the fully concise form.

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 4-parameter tool with no output schema. It explains only the URL-citation behavior and omits the json and zone operations entirely, leaving an agent unsure how these parameters interact (independent operations? mutually exclusive?) and what responses to expect for non-URL 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. The description adds meaning for the url parameter by mapping it to the returned host/scheme/status, but it does not add any semantics to the json or zone parameters beyond what their schema descriptions already state ('JSON text to validate; discarded after the check' and 'IANA timezone name').

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

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

The description states a specific verb and resource: "Return host, scheme, and HTTP status for a URL." This is clear and not a tautology. However, the schema includes parameters for json validation and timezone (zone) that the description completely ignores, so the stated purpose only covers part of the tool's interface.

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 exclusions, and no prerequisites. The note 'Page content is not stored' hints at a lightweight operation but does not help an agent decide when to invoke this tool over a sibling.

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 contributes one useful behavioral fact: 'No identifiers are retained.' However, with no annotations at all, it fails to disclose whether this operation has side effects, whether any input is persisted or transmitted, what processing is performed, or what the response contains.

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 brief and the privacy note is useful, but the brevity is not backed by structure or front-loaded detail that would help an agent understand the tool. It reads more as under-specification than as disciplined conciseness.

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

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

With four optional parameters, no output schema, no annotations, and a highly vague name, the description is fundamentally inadequate. An agent cannot determine which input(s) to provide, what classification will be returned, or how this relates to the sibling tools, making correct invocation essentially guesswork.

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 describes all four parameters fully, so schema coverage is 100% and the baseline is 3. The description itself adds no parameter-level meaning, leaving it unclear which parameter(s) the classification operates on.

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?

'Show how this request is classified' conveys a verb and a vague resource, but the description never says what 'request' refers to, how it is classified, or what classification means. It does not meaningfully differentiate this tool from siblings like normalize-url, validate-json, or citation.

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

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

There is no guidance about when to use this tool instead of an alternative, no mention of which inputs are appropriate, and no exclusions or prerequisites. The agent is left to infer usage from the tool name and schema alone.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose one limitation (no WHOIS/ownership enrichment), but it fails to disclose the JSON-validation and timezone behaviors implied by the schema, nor any output or error characteristics. The unmentioned behaviors are a significant transparency gap.

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

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

The description is a single, front-loaded sentence with no filler; the verb and resource appear immediately. It is efficient, though the brevity sacrifices coverage of the schema's broader scope.

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 spanning at least three apparent concerns (URL/host handling, JSON validation, timezone naming) and no output schema, the description covers only the hostname-splitting aspect. An agent would not know what the response looks like or how the json and zone parameters behave in practice.

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 and the schema already documents all four parameters. The description adds no parameter-level meaning, and its singular focus on hostname splitting conflicts with the presence of json and zone parameters, creating confusion rather than clarification.

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

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

The description states a specific verb ('Split') and resource ('a hostname into labels'), and the negative constraint ('without WHOIS or ownership data') helps scope the operation. However, the input schema's json ('JSON text to validate') and zone ('IANA timezone name') parameters imply additional functionality the description omits, so the stated purpose doesn't fully match the tool's apparent surface. This mismatch muddies what the tool actually does.

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

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

The phrase 'without WHOIS or ownership data' implies a limitation but provides no explicit when-to-use or when-not-to-use guidance. No alternative sibling tools are named, so an agent can't tell when to pick this over normalize-url, validate-json, or zone-count.

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, but it only names a category of data and gives no indication of return values, side effects, input handling, or whether this is a read-only lookup. It is too underspecified to predict what happens when called.

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 with no wasted words, but this is under-specification rather than effective conciseness. It is a noun phrase without front-loaded action, and it does not structure the essential information an agent needs.

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 annotations, and no output schema, the description needs to explain what the tool returns, which parameters are relevant, and why url/host/json are accepted. It does none of this, leaving the tool effectively opaque.

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 detail. However, the schema's individual descriptions are clear but poorly aligned with the stated purpose—only 'zone' obviously relates to IANA timezone names, while url/host/json seem borrowed from sibling tools.

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 a resource—'Common IANA timezone names'—and a use context ('for clock calls'), but it lacks a verb, so it never explicitly says what the tool does (e.g., list, return, or filter). It is distinguishable from timezone/utc-time only by implication, and the unrelated url/host/json parameters muddy the 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?

The phrase 'for clock calls' implies it should be used when supplying a timezone to clock-related tools, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives among siblings such as timezone, utc-time, or zone-count. An agent is left to infer the selection criteria.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It states a network fetch and count-only output, but does not disclose error handling, size limits, redirects, whether robots.txt parsing is case-insensitive, or what 'group counts' precisely means. The description also gives no hint that unrelated parameters like json or zone might affect behavior.

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

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

The description is a single front-loaded sentence with no filler words. It is efficient and easy to parse, but it may be too terse given the mismatch between the stated purpose and the broader schema.

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 parameters, no required fields, no annotations, and no output schema, the description is insufficient. It does not explain how the parameters map to the robots.txt fetch, what 'group counts' actually counts, or whether the other parameters (json, zone) are used at all. Agents cannot reliably determine correct 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 coverage is 100%, but the parameter descriptions in the schema are misaligned with the tool's stated purpose: 'url' is described as 'HTTPS URL to normalize or cite', 'json' as 'JSON text to validate; discarded after the check', and 'zone' as 'IANA timezone name' — none of which relate to fetching robots.txt. The tool description adds no parameter-level clarification, so the agent receives conflicting or irrelevant semantics.

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

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

The description gives a specific verb ('Fetch'), a clear resource ('public robots.txt'), and a precise outcome ('return group counts only'). It also uses 'only' to signal a narrow scope. However, it does not differentiate itself from the sibling tools by name, and the input schema's parameters (json, zone) suggest additional behaviors not mentioned.

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 the siblings (citation, normalize-url, validate-json, timezone). The only implied usage is 'when you need robots.txt group counts,' but the presence of json and zone parameters alongside siblings that handle those concerns makes the selection unclear.

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

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

With no annotations, the description carries the behavioral disclosure burden. It usefully discloses that query strings and fragments are dropped, which is a real behavior beyond the basic operation. However, it does not explain side effects, error cases, or why unrelated parameters like json and zone 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?

The description is a single front-loaded sentence with no filler or repetition. Every word contributes meaning, making it easy to parse quickly.

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 four optional parameters, yet the description only covers the URL-origin/host/path output. It does not define the return shape, behavior when url is absent, or what json, host, and zone parameters are for, so an agent cannot fully anticipate the tool's 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 structured fields already document each parameter. The tool description does not need to repeat them. Still, it fails to clarify how host, json, and zone relate to the stated URL-normalization purpose, leaving the parameter semantics ambiguous.

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 and resource: 'Return origin, host, and path for a URL.' This clearly identifies the core normalize/parse operation. It does not explicitly differentiate from sibling tools, but the behavior is concrete enough for an agent to understand the tool's role.

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, nor does it state prerequisites or expected inputs. The only implied usage is 'for a URL,' and no exclusions or sibling-tool branching are mentioned.

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

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

With no annotations, the description carries the full burden of disclosing behavior. It only states that the tool contains a catalog; it does not explain what happens to the inputs, whether there are side effects, what the output is, or what 'normalize or cite' vs 'validate' mean in 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 short and front-loaded, but it is under-specified rather than genuinely concise. The single sentence does not earn its place because it omits the tool's core action and leaves the parameter relationships unexplained.

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 unrelated-looking parameters, no output schema, and no annotations, this description is inadequate. An agent could not confidently determine how to invoke the tool correctly or 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?

Schema description coverage is 100%, so each parameter is individually documented, which meets the baseline. However, the description itself adds no connection between these parameters and HTTP status codes, leaving semantic ambiguity about why they are accepted 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 says this is a 'short catalog of common HTTP status codes,' but it does not say what the tool actually does with the provided parameters (url, host, json, zone). There is no clear verb indicating an action, and it does not differentiate itself from sibling tools like citation or compatibility.

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 for when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or exclusions, leaving the agent to guess how status codes relate to the provided inputs.

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

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says the current time is returned. It does not state output format, error behavior, or that url, host, and json appear to be unrelated schema fields.

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

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

The description is one short, front-loaded sentence with no filler, so it is concise. Its brevity is a weakness in coverage, but as pure conciseness it earns a decent score.

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

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

The tool has a confusing four-parameter schema, no annotations, no output schema, and several related siblings, yet the description provides only minimal functional information. It leaves the agent uncertain about which inputs are needed, what the result looks like, and how this tool relates to utc-time or iana-zones.

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% parameter descriptions, but only zone matches the tool's stated purpose; url, host, and json look like fields from other tools and are not reconciled with the timezone functionality. The description adds meaning for zone but does not explain whether the other parameters are accepted, ignored, or required, especially since all parameters are optional.

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 that the tool returns the current time in a named IANA timezone, giving it a specific verb-resource pairing that is distinguishable from a generic UTC clock. It does not explicitly call out sibling tools like utc-time or iana-zones, but the intent is reasonably clear.

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

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

There is no guidance about when to use this tool instead of siblings such as utc-time, iana-zones, or zone-count. The description also gives no hints about required inputs or how to handle invalid timezone names.

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 does not specify the output format (Unix epoch vs ISO 8601), precision, or whether the four optional schema properties are accepted or ignored. This ambiguity matters for correctly using the returned timestamp.

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 or repetition. It loses one point only because its extreme brevity omits the behavioral and parameter context needed elsewhere.

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 clock tool a short description can be complete, but this one misses two essential pieces of information: the exact return representation and the role, if any, of the four optional parameters. The presence of an apparently unrelated input schema makes the description incomplete 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?

The input schema documents each parameter individually, so schema coverage is 100%, but the description does not explain why url, host, json, or zone would be relevant to obtaining the current UTC time. The description adds no semantic connection between the parameters and the operation, and the mismatch is confusing.

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

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

The phrase 'Current UTC timestamp' clearly identifies a read-only operation that returns the present UTC time. It is unambiguous on its own, though it does not explicitly name a verb and does not differentiate itself from the sibling 'timezone' 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 use utc-time versus timezone, iana-zones, or zone-count. The description only states what the tool returns, leaving selection and invocation context 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. It does disclose a meaningful behavioral trait — 'The body is discarded' — indicating the operation is non-persistent and safe. However, it does not say what the tool returns (e.g., boolean, error on invalid JSON), which is important since there is no output schema.

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 wasted words, and the primary behavior is front-loaded. The slight use of 'body' instead of 'json' introduces a minor terminological inconsistency, but overall this is tight and efficient.

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, yet the description does not explain the return format or error semantics, which an agent needs to interpret the result. Additionally, the schema lists three parameters that appear irrelevant to JSON validation, and the description does not resolve this confusion.

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 the discard-behavior context that maps to the 'json' parameter, but it refers to 'body' rather than 'json', creating slight ambiguity. The other three parameters (url, host, zone) are unrelated to JSON validation and receive no clarification in the description.

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

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

The description states a specific action ('Check whether a body is valid JSON') with a clear verb and resource. It is distinguishable from the sibling tools, which are all about URL, timezone, or citation concerns. The term 'body' is slightly vague since the actual parameter is named 'json', but the intent is clear enough.

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

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

No guidance is given on when to use this tool versus alternatives, and no exclusions or conditions are stated. The usage context is only implied: you use it when you need to verify JSON validity. There is no comparison to any sibling 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?

No annotations are provided, so the description carries the full burden of explaining behavior. 'Common zone count' discloses nothing about side effects, return format, errors, or processing semantics, making the tool essentially a black box.

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 worthwhile conciseness. A three-word phrase cannot adequately describe a tool with four parameters and ten similar sibling tools.

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, no required parameters, and a highly ambiguous description, the definition is completely inadequate. An agent cannot determine what to pass, what to expect back, or how zone-count differs from related tools like iana-zones.

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 individual parameter descriptions already convey their surface meaning. However, the tool description adds no value about how the parameters relate or which combination should be used, so it does not exceed the baseline.

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 'Common zone count' is a vague noun phrase that essentially restates the tool name without stating a specific verb, resource, or outcome. It does not clarify whether the tool counts zones, returns a count, or does something else entirely, and it fails to distinguish itself from siblings like iana-zones.

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

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

There is no guidance on when to use this tool versus any of its siblings such as timezone, utc-time, or validate-json. With four optional parameters and no required ones, an agent has no basis for deciding which inputs to provide or when this tool is appropriate.

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