Language he

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 states 'Returns connection methods' and 'Task text discarded,' but it's unclear what 'task text' refers to since there's no corresponding parameter. It doesn't disclose side effects, network usage, cost implications (despite mentioning pay-per-call), or any rate limits. The disclosure is minimal and confusing.

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 two sentences, front-loading the purpose and adding a behavioral note about discarded task text. It is efficient and free of fluff, earning a high score for 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?

The tool has 9 optional parameters with no required ones, but the description doesn't clarify how an agent should specify the desired task. The phrase 'Task text discarded' is ambiguous since no task-text parameter exists, and the output ('connection methods') is undefined without an output schema. An agent lacks the information needed to call this tool correctly.

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

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

The input schema provides 100% coverage with each parameter having a descriptive comment (e.g., 'City name for a public weather hint; discarded after the call'). The description itself doesn't add meaning beyond the schema; it doesn't explain how parameters relate to the task selection or what 'connection methods' mean. Baseline 3 is appropriate given the schema already documents parameters well.

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 purpose: 'Find a public pay-per-call tool gateway for a task such as weather, search, scrape, or voice.' It specifies the verb (find), resource (gateway), and gives examples. However, it doesn't explicitly differentiate itself from the many sibling tools that serve similar task domains, so it's clear but not sharply distinguished.

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 when to use the tool (for tasks like weather, search, scrape, or voice) but provides no explicit guidance on when not to use it or how it relates to alternatives. It doesn't mention any of the sibling tools or explain that specific parameter choices select a task. An agent would struggle to know whether to use this tool versus a more specific sibling like weather-hint or validate-json.

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

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

With no annotations, the description carries the full burden. The only behavioral disclosure is that no browser is launched; it does not state whether a network request is made, what 'can be opened' means, whether there are side effects, or what failure modes 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 extremely concise: two short sentences with no redundant wording. It front-loads the main action and adds one important caveat about browser behavior.

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 too sparse for the tool's complexity: no output shape, no success/failure criteria, no mention of how the nine optional parameters are used, and no relationship to sibling tools. An agent would not know what result to expect or how to interpret the response.

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 nine parameters have individual schema descriptions, so the baseline is met. However, the tool-level description does not explain why parameters like city, feed, json, path, zone, or query relate to checking a URL, leaving the overall parameter model confusing despite per-field 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 an action ('check') and a clear target ('whether a URL can be opened'), and it explicitly notes that no browser is launched. It does not, however, differentiate this from sibling tools such as playwright-url-ok, fetch-status, or normalize-url, so the purpose is only mostly 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?

No guidance is provided about when to use this tool instead of the many related URL/status/fetch siblings. The description gives no conditions, prerequisites, or selection criteria, so an agent must infer usage from the tool name 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?

With no annotations, the description carries the burden for behavioral disclosure, but it only says the expression is discarded; it does not explain side effects, failure modes, or why an expression would be discarded.

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

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

The text is short, but the second sentence adds confusion rather than useful structure, and the description omits the essential input mapping.

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 nine optional, unrelated parameters and no output schema; the description is insufficient for an agent to know what to pass or what result to expect.

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

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

All nine parameters have descriptions, but none of them represents an arithmetic expression, and the description does not connect any parameter to the tool's stated purpose; the schema is effectively unusable for the advertised operation.

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

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

The description states a clear verb and object ('Evaluate a+b style arithmetic'), but no input parameter for an expression exists in the schema, and 'Expression discarded' makes the actual operation ambiguous.

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

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

There is no guidance about when to use this tool instead of any sibling tool, and no context about call patterns or expected 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 provided, the description must carry the behavioral disclosure burden. It does state 'Page content is not stored,' which is a useful behavioral trait. However, it omits other important aspects such as whether the tool makes network requests, follows redirects, or requires authentication. While the statement about not storing content adds value, the overall behavioral context is thin.

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

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

The description is a single, well-structured sentence that immediately states the core function and then adds a relevant behavioral note. It is concise, front-loaded, and contains no filler. Every word earns its place, making it an exemplary model of brevity.

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 9 parameters, the description only addresses the URL aspect and ignores the other parameters entirely. It does not clarify whether those parameters are simply ignored, checked, or part of a broader capability. Additionally, there is no output schema, so the agent does not know the format of the returned host, scheme, and HTTP status. The description is too minimal to fully equip an agent to use this tool correctly among many similar siblings.

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

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

Schema description coverage is 100%, so each parameter has a description in the schema. The tool description adds no additional meaning about parameters—it only refers to 'a URL' without specifying which parameter to use. The schema itself clarifies that 'url' is for the URL, but the tool description does not reinforce this or explain the role of the other 8 parameters. Since coverage is high, the baseline of 3 is appropriate, but the description fails to compensate for the many seemingly irrelevant parameters.

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

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

The description states a clear purpose: 'Return host, scheme, and HTTP status for a URL.' This is a specific verb and resource, making it easy to understand what the tool does. However, it does not distinguish itself from siblings like 'fetch-status' or 'browser-url-ok', which likely have overlapping functionality, so it doesn't fully achieve a 5.

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 description does not mention any conditions, prerequisites, or explicit comparisons to sibling tools. An agent has no direction on when to prefer 'citation' over similar tools, leaving this decision 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, the description bears the full burden of disclosing behavior. It only states 'No identifiers are retained,' which is a limited privacy note, but it does not explain side effects, read-only status, or what processing occurs.

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 too terse to be useful. It omits necessary details about the classification process and parameter relationships, making the brevity a drawback rather than an asset.

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 9 parameters, no output schema, and no annotations, so the description must provide sufficient context. It does not explain what output form the classification takes, how to interpret results, or how the parameters influence the outcome, leaving the tool largely unusable.

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 parameter descriptions are incoherent for a single tool. Terms like 'discarded after the shape check,' 'normalize or cite,' and 'public weather hint' suggest they are copied from other tools and do not clarify how each parameter is used for this classification 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 'Show how this request is classified' is vague and does not specify the tool's actual function or resource. It does not distinguish this tool from any of the 26 siblings, and the name 'compatibility' does not clarify the behavior.

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 alternative. The description lacks any indication of what request types are suitable, what the classification means, or how it relates to sibling tools.

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

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

No annotations are provided, so the description carries the burden of explaining behavior. It does state that no WHOIS or ownership data is involved, implying no external lookup, but it does not explicitly mention side effects, data retention, or whether the operation is read-only.

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, focused sentence with no redundant words. It clearly states the core operation and an important limitation in a concise way.

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 nine optional parameters, no required parameters, and no output schema, the description is far too minimal. It does not specify which input to provide, what output format to expect, or how errors are handled, making the tool effectively unusable based solely on the description.

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 description mentions hostname, so 'host' is the only obviously relevant parameter, but the schema includes eight other optional parameters (ref, url, city, feed, json, path, zone, query) with unrelated or 'discarded' descriptions. The description does not clarify which parameters are actually needed, leaving invocation 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 gives a specific action and object: 'Split a hostname into labels', and scopes it with 'without WHOIS or ownership data'. However, the tool name 'domain-shape' suggests validation/shape-checking, which is not explicitly stated in the description.

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

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

The description offers no guidance on when to use this tool versus alternatives like figma-url-shape, github-repo-shape, or normalize-url. The only hint is the negative phrase 'without WHOIS or ownership data', which does not explain when this tool should be selected.

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 disclose side effects, ignored inputs, and error behavior itself. It does state HEAD and status-only, and some parameter descriptions mention discarded values, but the main description does not explain how the many unrelated parameters are handled, redirects, or failure modes.

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 focused sentence with no filler or repetition. It is front-loaded and easy to scan.

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

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

The tool has nine optional parameters and no output schema, but the description only says 'return status only.' It does not specify which parameter is the URL target, what exact status is returned, how ignored fields are treated, or what happens on network errors or redirects, so an agent cannot reliably 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?

Every parameter has a description, but most descriptions are disconnected from the stated HEAD-URL purpose and several explicitly say they are discarded or only checked for shape/length. The 'url' parameter is described as 'to normalize or cite' rather than as the target of the HEAD request, so the schema does not clarify which field drives the operation.

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 names a clear action and resource ('HEAD a public URL and return status only'), but the input schema exposes many unrelated optional fields (city, json, path, zone, query), so the intended scope is muddied. It only weakly distinguishes from sibling URL tools like web-fetch or browser-url-ok.

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 choose this tool over alternatives such as browser-url-ok, web-fetch, or status-catalog. The phrase 'status only' implies a use case, but there is no explicit when-to-use or when-not-to-use instruction.

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 only mentions that the path is discarded. It does not disclose whether the tool performs network access, validates the URL, returns errors, or has side effects.

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 and free of padding. Every sentence adds a small piece of information, and it is front-loaded with the main purpose.

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

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

There is no output schema, no return-value description, no examples, and no required parameters. With nine optional parameters and generic descriptions, an agent cannot reliably know how to invoke the tool 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?

Although all parameters have schema descriptions, those descriptions are generic and some are unrelated to Figma URL parsing (e.g., city, feed, zone, query). The description does not clarify which of the 9 optional parameters are relevant, and the url parameter description ('normalize or cite') conflicts with the parse 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 states a concrete action ('Parse a Figma file URL') and a boundary ('Path discarded'), but it does not say what output is produced or what 'shape' means. This leaves the tool's purpose only partially specified.

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 choose this tool over sibling tools like normalize-url, browser-url-ok, or web-fetch. It does not mention that it is only for Figma file URLs, nor what inputs are inappropriate.

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, and the description only discloses that the tool performs no disk access. It does not mention return values, success/error behavior, or whether it validates syntax only—leaving the tool's observable behavior largely unspecified.

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, using two short sentences to convey the primary purpose and a key behavioral guarantee. It wastes no words, though it could benefit from a little more specificity.

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 output schema, no usage examples, no return-type information, and no indication of which parameter to pass, the description leaves critical context missing. An agent would not be able to reliably interpret the result or know how to formulate a valid 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?

Although the schema has 100% description coverage, most of the parameters (ref, url, city, feed, host, json, zone, query) appear irrelevant to the stated purpose of checking a file path. Only 'path' is clearly relevant, and the presence of many unrelated optional fields creates confusion about what the tool actually accepts.

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 checks whether a path looks safe and explicitly notes no disk access, which distinguishes it from sibling URL and domain checkers. However, 'looks safe' is somewhat ambiguous—it does not specify what safety criteria are checked.

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 like browser-url-ok or normalize-url, and it does not explain which of the nine schema parameters should be provided. It only notes the absence of disk access, which is a minimal safety signal.

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, but it only mentions the use of Open-Meteo. It does not explain side effects, error behavior, what happens when no place is identified, or whether the operation is read-only.

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 compact and free of fluff, with one clear sentence. It loses a point only because the brevity omits essential usage 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?

Given the tool has nine optional parameters and no output schema, the description is too incomplete to enable correct use. It does not explain how to provide a place, what the response looks like, or what the 'discarded' parameters imply.

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 descriptions exist for all parameters, they are mostly unrelated to geocoding and several explicitly say the value is 'discarded after' a check. The description does not clarify which parameters are meaningful for geo-hint, so the schema adds confusion rather than useful input semantics.

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

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

The description states the tool returns latitude and longitude for a place via Open-Meteo, which conveys the core purpose. However, it does not specify which of the nine optional parameters should be used to identify the place, leaving the intent ambiguous.

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

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

There is no guidance on when to use this tool versus alternatives such as weather-hint or timezone, nor any indication of which parameter to supply. The description simply states what it does, not when or how to invoke it effectively.

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 verb 'parse' suggests a read-only operation, and some schema descriptions mention discarded values or no disk access, implying no persistent side effects. However, the tool description itself does not explicitly state whether network access, authentication, or any mutation is involved.

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 redundant wording. It directly states the action and target.

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 gives the core purpose but omits the return format, behavior for invalid URLs, and which optional parameter to provide. Given the broad and ambiguous schema, this leaves important operational context missing.

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 is largely misaligned with the stated purpose: the url parameter is described as 'normalize or cite' rather than as a GitHub URL, and eight unrelated optional parameters are present. The tool description provides no guidance on which parameter should actually be used to parse a GitHub repository.

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 action and resource: parse owner and repo from a GitHub URL. This distinguishes it from sibling shape tools focused on domains, Figma URLs, or Jira keys.

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 explicit guidance is given for when to use this tool versus alternatives such as normalize-url, domain-shape, or figma-url-shape. The intended use is only implicit: when a GitHub repo owner and name need to be extracted.

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 only states that the tool counts stories and discards titles. It does not explain whether the count is live, how errors are handled, or any side effects.

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 mostly direct. The phrase 'Titles discarded' is a bit odd but does not add significant clutter.

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 core action is simple and could be invoked with no arguments, but the nine optional parameters are unexplained and irrelevant-sounding. There is no output schema, so an agent has limited context about the exact return value.

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 descriptions for all parameters, they are generic and unrelated to counting Hacker News stories (e.g., 'Git ref name; discarded after the shape check'). The description does not connect any parameter to the tool's actual function.

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's purpose: counting current Hacker News front-page stories. It uses a specific verb and resource, though 'Titles discarded' is slightly ambiguous.

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

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

There is no guidance about when to use this tool rather than the many sibling tools, such as web-fetch or browser-url-ok. No prerequisites or context 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?

No annotations are provided, and the description does not disclose side effects, return value, required parameters, or any behavioral details. The tool's actual operation is entirely 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?

The description is concise and free of fluff, but it is so minimal that it fails to convey the tool's function. It is appropriately short but not effectively structured.

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 parameters, no output schema, and no annotations, the description is far too incomplete. It does not explain what the tool returns, how the parameters are used, or even the 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?

Although the schema descriptions cover all 9 parameters, most are irrelevant to IANA timezone names (e.g., 'HTTPS URL to normalize or cite', 'File path to check'). Only 'zone' is plausibly aligned, but the overall parameter semantics are misleading.

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

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

The description is a noun phrase ('Common IANA timezone names for clock calls') that restates the tool name without specifying an action or clear purpose. It does not distinguish this tool from siblings like timezone or utc-time.

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

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

No guidance is given on when to use this tool versus alternatives such as timezone or utc-time. There is no mention of use cases, prerequisites, or expected 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?

The description indicates a read-only fetch operation but does not disclose any potential side effects, caching behavior, or error conditions.

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, concise sentence, but the input schema includes many irrelevant parameters that could be trimmed for clarity.

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

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

The tool lacks an output schema and critical usage context, such as which parameter specifies the target URL and what the returned group counts look like, leaving the agent uncertain about how to call 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?

The 9 optional parameters have descriptions that are mismatched with the tool's purpose (e.g., 'Git ref name', 'City name for weather') and do not clarify which parameter is used for the robots.txt URL, making it impossible to know how to correctly invoke 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 fetches a public robots.txt and returns group counts, which is specific and distinct from sibling tools like web-fetch or fetch-status.

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 mention of when to use this tool over alternatives such as web-fetch or fetch-status, nor any conditions that would favor this 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?

With no annotations and a terse description, the tool's behavior is opaque. It does not state what happens on success/failure, whether it returns a boolean, throws, or has side effects. 'Key discarded' hints at no return but is insufficient.

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 sentence, which is concise, but it lacks structure. It provides no breakdown of parameters, expected inputs, or outputs, making it minimally acceptable but not well-organized.

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 nine optional parameters and no output schema, the description is severely incomplete. It does not explain the tool's purpose in context, how parameters interact, or what the caller should expect, leaving critical gaps for an agent.

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 parameter descriptions are generic and largely irrelevant to Jira keys (e.g., 'city', 'feed', 'zone'). They do not clarify how each parameter relates to the Jira key check, and the descriptions add no meaning beyond the parameter names—some are misleading (e.g., 'ref' as 'Git ref name' in a Jira context).

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 ('Check') and resource ('Jira issue key shape'), but it does not indicate which of the nine parameters holds the key, leaving ambiguity about the tool's actual input. It also mentions 'Key discarded' without specifying the output, reducing clarity.

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

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

No guidance is provided on when to use this tool versus the many sibling validation tools (e.g., browser-url-ok, file-path-ok, validate-json). There is no mention of context, alternatives, or 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?

No annotations are provided, and the description does not explain behavior, side effects, return values, or permissions. Parameter descriptions mention 'discarded', but this is not tied to an overall behavioral explanation.

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 brief and free of filler, but it is a fragment without a clear verb or structured explanation. It is concise but not effectively structured.

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 parameters, no output schema, and no annotations, the one-line description is far from sufficient to understand the tool's full behavior, return format, or appropriate usage.

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

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

While the schema covers all 9 parameters with descriptions, those descriptions are unrelated to the stated purpose of a language tag. The 'discarded' notes suggest inputs are ignored, but the connection to 'he' is 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?

Description is a noun phrase ('ISO 639 language tag he.') rather than a clear verb phrase. It does not explicitly state whether the tool returns, validates, or converts the tag.

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 any sibling tool. The description lacks any context for selecting 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?

The only disclosed behavior is that the body is discarded, which is useful. With no annotations, the description carries the full burden, but it omits other relevant behaviors such as redirect handling, errors, or network-side effects.

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: two sentences, no filler, and every word contributes meaning.

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 output schema and no annotations, the description leaves too much unspecified. It does not explain which of the nine parameters to provide, whether the others are ignored, or what the returned status looks like.

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

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

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter mapping, and some schema property descriptions seem inconsistent with the stated purpose (e.g., url is described as 'HTTPS URL to normalize or cite').

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 the basic action: return an HTTP status for a public library docs URL and discard the body. However, 'public library docs URL' is vague, and the description does not differentiate this tool from sibling URL/status tools like fetch-status or browser-url-ok.

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. There is no mention of when to use this tool instead of the many sibling URL/status tools, nor any condition for selecting 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?

With no annotations and only a two-sentence description, the tool does not disclose return values, error behavior, side effects, or edge cases. 'Values discarded' hints at behavior but leaves almost everything unspecified.

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 and easy to read, but it omits essential information. It is concise to the point of being unhelpful rather than efficiently informative.

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 nine parameters, no output schema, no annotations, and a minimal description. The description does not explain what the parameters do, what output is produced, or how the tool fits into a workflow. It is far from complete.

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 every parameter has a schema description, the descriptions appear unrelated to the stated purpose of counting keys in a JSON object. For example, 'json' is described as 'JSON text to validate; discarded after the check', which suggests validation, not key counting. The parameter semantics are confusing and inconsistent.

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

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

The description states a clear action ('Count keys in a JSON object') but does not explain how this relates to the many unrelated parameters or distinguish it from sibling tools like validate-json 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?

No guidance is provided about when to use this tool versus alternatives, when not to use it, or what kind of input is expected. The description gives no practical 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?

The description only mentions that query and fragment are dropped. It does not disclose behavior for invalid or missing URLs, output format, or whether any network access occurs; there are no annotations to cover these 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?

The description is two short sentences with no fluff. It immediately states what is returned and what is discarded, making it very 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?

Given the tool has 9 optional parameters and no output schema, the description is incomplete. It does not specify the return structure, error behavior, or which parameters are actually required or meaningful for the operation.

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 9 optional fields, many seemingly irrelevant to URL normalization. The description does not explain why ref, city, feed, json, path, zone, or query are accepted, and the query parameter's schema description conflicts with the tool description's use of 'query' as part of the URL.

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 origin, host, and path for a URL, and explicitly notes that query and fragment are dropped. This makes the core purpose unambiguous.

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

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

No guidance is provided on when to use this tool versus sibling tools like web-fetch or fetch-status, and no conditions or prerequisites 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?

The only behavioral note is 'No browser is launched,' but it does not disclose whether a network request is made, what side effects occur, what success/failure looks like, or what the return value 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 very short, but it is under-specified for a tool with nine parameters. The single sentence is not front-loaded with the most important usage information and leaves too much unsaid.

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

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

There is no output schema, no return value description, no error explanation, and no mention of network usage or side effects. Given the tool's ambiguous name and many parameters, the description is not sufficient for an agent to use 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?

Each parameter has a short description, but most are unrelated to the stated purpose of checking a URL (e.g., city, feed, json, zone). Terms like 'discarded after the shape check' are unclear and do not explain how the parameters relate to the tool's main behavior.

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 general action ('Check whether a URL can be opened') but immediately undercuts it with 'No browser is launched,' leaving the actual mechanism unclear. It also does not distinguish this from sibling tools like browser-url-ok or fetch-status.

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

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

There is no guidance on when to use this tool versus the many similar sibling tools. No conditions, prerequisites, or example use cases 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 burden of transparency. It discloses that the query is discarded, but it does not describe the return value, error behavior, or any other side effects.

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 unnecessary detail or repetition. It is direct 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 does not specify the output format, what happens when no query is provided, or whether a query is effectively required despite the schema listing zero required parameters. These gaps leave important invocation details unspecified.

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?

Every parameter has a description. The 'query' parameter is clearly identified as the search text used for the length check, and the other parameters are explicitly marked as discarded or irrelevant, which helps clarify their role despite being unusual for this 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 counts characters in a search query and explicitly notes that the query is discarded. The verb 'count' and the target 'characters in a search query' are specific and unambiguous.

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

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

No guidance is provided about when to use this tool versus sibling tools, when it is appropriate, or when it should be avoided. The description only states what it does, not when to choose 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?

There are no annotations provided, and the description discloses no side effects, permissions, or read-only nature. The tool's behavior is entirely opaque; it is unclear whether it performs network requests, reads files, or purely returns static data. No behavioral expectations are set.

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

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

The description is concise but far too sparse. It is a single sentence that omits essential details about parameter usage, return format, or tool behavior. While brevity is a virtue, here it sacrifices clarity and leaves critical gaps that should be filled for effective tool selection and invocation.

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 the schema (9 parameters, no output schema) and the confusing parameter descriptions, the description is grossly incomplete. It does not clarify the role of the parameters, the expected output, error handling, or any constraints. The agent cannot confidently predict what the tool does or how to call 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?

The description adds no meaning to the parameters. The schema lists nine unrelated parameters (e.g., 'ref', 'url', 'city', 'zone') with descriptions that appear mismatched (e.g., 'Git ref name; discarded after the shape check'), none of which clearly relate to HTTP status codes. The description fails to explain how any of these parameters influence the catalog output, leaving the agent completely in the dark.

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

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

The description states a clear primary purpose: 'Short catalog of common HTTP status codes.' However, it is extremely brief and does not elaborate on how the tool provides this catalog or what kind of output to expect. The vague phrasing leaves room for interpretation, especially given the unrelated parameter names.

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 indicate when to use this tool over alternatives like 'fetch-status' or 'browser-url-ok', nor does it mention any prerequisites or context. The agent is left without criteria to select this 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?

The description explicitly states 'Prompt discarded,' which is a key behavioral disclosure that the tool ignores its input. Since annotations are absent, this note carries the full burden and is transparent about the tool's side-effect-free, read-only nature. However, it does not mention broader aspects like auth or rate limits, but for this simple tool that is acceptable.

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 exceptionally concise, consisting of two short sentences. It front-loads the core purpose and then notes the discarded prompt. There is no unnecessary verbosity.

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 9 parameters, none required, and no output schema. The description does not explain why there are so many parameters, which ones are relevant, or what the 'three-step thinking template' looks like. The note 'Prompt discarded' is ambiguous about whether structured parameters are ignored or just the free-text prompt. This leaves the agent without enough context to invoke the tool correctly.

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

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

The input schema has 100% description coverage, giving a baseline of 3. However, the tool description adds no meaning to the parameters and actually contradicts the parameter descriptions. The parameters are described as being used for specific tasks (e.g., 'HTTPS URL to normalize or cite'), but the tool description says it only returns a template and discards prompts. This confusion prevents the description from adding any semantic value beyond the schema.

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

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

The description clearly states the tool's function: 'Return a three-step thinking template.' The verb 'Return' and the object 'three-step thinking template' are specific, and the tool name 'think-steps' matches. It is easily distinguishable from sibling tools like 'calc-eval' 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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any conditions, use cases, or scenarios where this tool is preferred. The phrase 'Prompt discarded' gives no 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?

With no annotations, the description carries the full burden of disclosing behavior. It implies a read-only time lookup but does not mention side effects, error behavior, or that the many unrelated schema parameters appear to be ignored or discarded.

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

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

The description is concise and front-loaded with the core purpose in a single sentence. It does not waste words, though it sacrifices useful usage and parameter context for brevity.

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 confusing schema with nine optional parameters, most unrelated to timezone lookup. It does not specify which parameter is required/expected, what happens with ignored parameters, or what the return value contains.

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% parameter description coverage, most descriptions are irrelevant to a timezone tool (e.g., 'Git ref name', 'HTTPS URL to normalize', 'JSON text to validate'). The description only maps weakly to the 'zone' parameter and does not clarify that the other optional parameters are not meaningful for this 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 identifies the tool's purpose as returning the current time for a named IANA timezone, which is specific enough to distinguish it from related tools like utc-time. However, it lacks an explicit verb such as 'gets' or 'returns' and does not describe the output format.

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 alternatives like utc-time or iana-zones. There are no examples, exclusions, or context to help an agent choose this tool over siblings.

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

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

There are no annotations, and the description does not disclose whether the operation is read-only, has side effects, requires permissions, or what the output format looks like. The tool's behavior beyond returning a timestamp is entirely 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?

The description is a single sentence with no unnecessary words, making it highly concise. However, it omits critical details, but that is a matter of completeness rather than conciseness; the structure is 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?

For a simple tool, the description fails to provide essential context: it does not specify the timestamp format (e.g., ISO 8601), how the parameters relate to the operation, or what the response contains. The confusing parameter descriptions exacerbate the incompleteness, leaving the tool's usage ambiguous.

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 includes 9 optional parameters, but their descriptions are nonsensical and unrelated to UTC time (e.g., 'Git ref name; discarded after the shape check', 'Search text; discarded after the length check'). These add no meaningful information and actively mislead, providing no value over the bare schema.

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

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

The description 'Current UTC timestamp.' clearly states the tool's purpose: it returns the current UTC time. This is specific and distinguishes it from sibling tools like 'timezone' or 'iana-zones', though it lacks elaboration on the exact format or additional details.

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

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

No guidance is provided on when to use this tool versus alternatives such as 'timezone' for timezone conversions or 'iana-zones' for zone lists. The description gives no context for selecting this tool among its siblings.

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 does mention that the body is discarded, which hints at no persistence, but it does not clarify side effects, output behavior, errors, or whether the many other schema parameters are ignored.

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

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

The description is concise and consists of two short sentences with no unnecessary verbose content. It could be slightly more informative, but it is well structured for its length.

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 nine optional string parameters, no required fields, and no output schema, the description is far too minimal. It leaves the agent unable to determine which parameters are relevant, how to supply the JSON, or what the tool returns.

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 descriptions for all parameters, but many appear unrelated (e.g., 'ref', 'url', 'city', 'feed', 'zone'). The description does not clarify which parameter contains the JSON to validate, and 'body' does not map cleanly to any parameter.

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. However, 'body' is ambiguous because the schema does not include a parameter named 'body' and the tool's exact return type is 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?

The description gives no guidance on when to use this tool versus alternative validation or fetching tools. It does not explain prerequisites, expected input, or how to interpret the result.

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. It mentions Open-Meteo as an external source, which is useful, but it does not disclose whether the tool makes a network call, whether it is read-only, or what side effects, if any, occur.

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: one sentence with no filler, redundant wording, or unnecessary detail. It is well-structured for quick parsing.

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

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

There is no output schema and no explanation of the return format, units, or error behavior. With no required parameters and a schema containing many seemingly unrelated optional fields, the description does not provide enough context for a caller to confidently invoke the tool.

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 every parameter has a description, most of the nine parameters are unrelated to 'current temperature for a city.' The schema includes ref, url, feed, json, path, zone, and query with plausible individual meanings, but the descriptions do not explain why they belong in a weather tool or how they relate to 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 is a single specific statement: 'Current temperature for a city via Open-Meteo.' It identifies the action (return current temperature), the subject (a city), and the data source (Open-Meteo), so the tool's primary purpose is 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 explicit guidance about when to use this tool versus the many sibling tools, nor any mention of when not to use it. The description implies it is for current city temperature, but it does not explain the intended selection criteria or exclude 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 present, and the description only vaguely mentions 'Body discarded.' It does not disclose side effects like network requests, potential external calls, or why most parameters are 'discarded', leaving side-effect behavior largely 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?

The main description is short and front-loaded, but the large parameter list makes the overall tool definition feel disjointed. It is concise in wording yet not structurally coherent enough for effective use.

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 nine parameters, no output schema, and no explanation of how parameters relate to the stated purpose, the description is far from complete. An agent cannot confidently determine valid combinations, expected inputs, or 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?

Although every parameter has a schema description, those descriptions are misleading or irrelevant to the stated HTTP-status purpose (e.g., 'City name for a public weather hint', 'File path to check; no disk access'). They add confusion rather than clarify how each parameter contributes to the tool's function.

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 outcome ('HTTP status and content type for a public URL') but is undermined by nine unrelated parameters (city, json, path, zone, query, etc.) that do not fit this purpose. It is not clear whether this tool is a narrow fetcher or a multi-purpose validator.

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 the many similar siblings (fetch-status, normalize-url, validate-json, etc.), nor any conditions or examples. The description provides no decision support.

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, and the description only vaguely mentions that the 'Title' is 'discarded after the call,' implying no persistence but not clarifying side effects, permissions, or failure behavior. This is insufficient for a tool with 9 parameters.

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

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

The description is extremely concise, using only two short sentences. It avoids unnecessary detail, which is good, though it sacrifices 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?

Given the complexity of the schema (9 parameters, no required fields, no output schema), the description is severely incomplete. It does not explain how to invoke the check, what the response looks like, or how the parameters relate to the 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?

The description does not map any of the 9 schema parameters to the 'title' it refers to. Although the schema descriptions exist, they are generic and unrelated to the tool's stated purpose, so the description adds no 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 the core action clearly ('Check whether a Wikipedia title exists'), but it does not specify which of the 9 input parameters corresponds to the title, making the purpose ambiguous in practice.

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

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

No guidance is provided on when to use this tool versus the many sibling tools that perform similar existence checks. It does not mention alternatives, prerequisites, or typical use cases.

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