Language gu

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

With no annotations, the description must carry behavioral details. It discloses 'pay-per-call', that it returns connection methods, and that task text is discarded, but it does not explain side effects, error behavior, or whether network requests are made.

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 and to the point, with no redundant words or filler. It fronts the purpose and gives a concise output note.

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 lacks essential context: how to invoke it with the optional parameters, what the connection methods look like, and what happens when no matching gateway is found. The schema helps but the overall tool behavior remains underspecified.

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 descriptions cover all 9 optional parameters, so the baseline is 3. The tool description adds no parameter-level information beyond what the schema already states.

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

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

The description states a clear verb ('Find') and object ('public pay-per-call tool gateway') with example tasks, but the term 'tool gateway' is vague and it is not clear what the returned 'connection methods' represent.

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?

It gives example tasks ('weather, search, scrape, or voice') but does not specify when to choose this tool over the many sibling tools or mention any alternative. No explicit when-to-use or when-not-to-use guidance.

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 says no browser is launched. It does not disclose whether a network request is made, what side effects occur, how failures are reported, or how the supplied parameters 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 short and front-loaded, but it is under-specified to the point of being unhelpful; brevity does not compensate for the missing semantic content.

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

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

There is no output schema, no usage context, no examples, and no explanation of return values or error behavior, so the tool cannot be used confidently from the provided information.

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 largely nonsensical for this tool (e.g., 'Git ref name', 'City name for a public weather hint', 'JSON text to validate') and do not explain how any parameter relates to checking whether a URL can be opened.

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 ('check whether a URL can be opened') but leaves 'can be opened' undefined—whether it means HTTP reachability, browser rendering, or something else—and does not differentiate it from sibling tools like fetch-status, web-fetch, or playwright-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 prefer this tool over the many similar sibling tools. The only extra information is a negative statement ('No browser is launched'), which does not establish 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 only vaguely says 'Expression discarded.' It does not clarify what is actually evaluated, what side effects occur, what the return value is, or why nine optional parameters 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 short but not appropriately informative. It is a cryptic fragment that raises more questions than it answers, and it is not front-loaded with useful orientation for an agent.

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

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

With no output schema, no annotations, and an incoherent parameter list, the description is far from complete. An agent cannot determine what inputs matter, what the tool returns, or what 'evaluate' means in this context.

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

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

Although every parameter has a schema description, the descriptions are mostly repetitive 'discarded after shape check' notes and none correspond to an arithmetic expression. The parameters appear irrelevant to the stated purpose, making the schema actively confusing rather than helpful.

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

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

The description says the tool evaluates a+b style arithmetic, but the input schema contains no expression parameter and instead lists nine unrelated string parameters that are all described as discarded. The purpose is incoherent and does not match the schema.

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

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

No guidance is given on when to use this tool versus any of the many sibling tools. The sibling list contains numerous more clearly named validators and checkers, but calc-eval gives no usage context at all.

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 only states that page content is not stored, but does not disclose that most parameters are discarded after shape checks, that no disk access occurs, or any other side effects or constraints. This is insufficient for a tool with 9 optional parameters.

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

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

The description is a single sentence that front-loads the core function and includes a relevant caveat. It is appropriately concise with no waste, though it could be slightly more informative given the tool's complexity. It earns a 4 because it is well-structured 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 description is incomplete for a tool with 9 parameters and no annotations or output schema. It lacks usage guidance, behavioral details about the discarded parameters, and any mention of what happens on invalid inputs. An agent would need to inspect the schema to understand the tool's full behavior, which is not ideal.

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% because every parameter has an explicit description. The tool description adds no extra meaning beyond the schema; it only implies the 'url' parameter is the primary input. Per the rubric, baseline is 3 when schema coverage is high, and no additional compensation is provided.

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

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

The description states a specific verb ('Return'), resource ('URL'), and output ('host, scheme, and HTTP status'). The additional note 'Page content is not stored' clearly differentiates it from content-fetching siblings like web-fetch or browser-url-ok, making the 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention conditions, exclusions, or reference sibling tools. An agent has no basis for selecting this over fetch-status or normalize-url based on the description 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 present, so the description carries the full burden. It does state that identifiers are not retained and that values are discarded, which is helpful, but it does not disclose what the tool actually does, whether it has side effects, or what output it produces.

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 concise and front-loaded, with no redundant wording. The brevity is a slight downside because it leaves the purpose ambiguous, but it is well-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 optional parameters and no output schema, the description is incomplete. It does not indicate what the classification result will look like, how parameters combine, or what 'compatibility' means in this context.

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

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

The schema descriptions cover all 9 parameters with brief meanings, and the tool description adds that values are discarded. However, it does not explain how each parameter influences the classification, which is important given that all parameters are optional and varied.

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 'Show how this request is classified' but does not explain what classification means, what categories are used, or how it relates to 'compatibility.' It does not distinguish this tool from sibling tools such as domain-shape or normalize-url.

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

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

There is no guidance on when to use this tool instead of the many sibling tools. No conditions, examples, or alternative references are provided.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It only explains hostname splitting but does not disclose what happens when other parameters (url, json, path, etc.) are supplied—whether they are ignored, validated, or discarded. The schema's per-parameter notes (e.g., 'discarded after the shape check') are not reflected in the description, leaving a significant gap.

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

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

The description is a single, concise sentence that front-loads the primary action ('Split a hostname into labels') and immediately adds a clarifying exclusion. No unnecessary words.

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

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

For a tool with 9 parameters and no annotations or output schema, the description is grossly incomplete. It covers only one input type (hostname) and says nothing about the tool's behavior with URLs, JSON, timezones, or search queries, nor about return values or error handling. An agent cannot determine when to call this tool versus its many 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 is already documented. The description adds no parameter-specific meaning beyond mentioning 'hostname' generically; it does not clarify how the 'host' parameter is used or how other parameters relate to the tool's core action. It stays at the baseline for high schema coverage.

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 (split a hostname into labels) and clarifies it excludes WHOIS/ownership data. However, the input schema accepts nine unrelated parameters (url, json, city, zone, etc.) that the description ignores, making the tool's actual scope ambiguous and failing to distinguish it from sibling shape-checking tools like 'validate-json' 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 on when to use this tool versus alternatives. The description does not mention that for URL validity one should use 'browser-url-ok' or that for JSON validation 'validate-json' is appropriate. The only hint is 'without WHOIS or ownership data', which is a limitation, not a usage criterion.

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 transparency burden, and it does disclose that the tool operates only on public URLs and returns status only. However, it omits important behaviors like redirect handling, timeout behavior, or error conditions, leaving significant gaps.

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 that gets straight to the point. It is well-structured and front-loaded with the essential action.

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 far from complete given the complex and confusing schema. It does not explain why the schema contains nine unrelated optional parameters, nor does it clarify which parameters the tool actually uses. The lack of an output schema also leaves the return format 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?

Despite high schema coverage, the parameter descriptions are inconsistent with the tool's stated purpose. The schema includes unrelated fields (Git ref, city, timezone, search text) with descriptions like 'discarded after the shape check' that are confusing and misleading for a URL status 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 performs a HEAD request on a public URL and returns only the status. This is a specific, unambiguous statement of the tool's core function.

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

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

The description gives no guidance on when to use this tool versus the many sibling tools such as browser-url-ok, playwright-url-ok, or web-fetch. There is no mention of alternatives, use cases, or exclusions.

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 mention side effects, permissions, or return format. It is unclear whether the tool performs network calls or purely local parsing.

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 with no redundant text. However, it is perhaps too terse, omitting essential details while maintaining 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?

With 9 optional parameters and no output schema, the description provides insufficient context to understand the tool's full behavior. It does not explain what 'shape' means, what the output looks like, or how parameters relate to 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 parameter descriptions seem unrelated to the tool's purpose (e.g., 'city' for weather, 'ref' for git), suggesting a template mismatch. It is unclear which parameters are actually used or what role each plays in parsing the Figma 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 states it parses a Figma file URL and discards the path, which is a specific action. However, the meaning of 'shape' is not defined, so it's not fully 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 on when to use this over other URL-related tools like normalize-url or domain-shape. The description provides no context for selection among 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?

The phrase 'No disk access' usefully discloses a safety behavior, but with no annotations the description still does not fully carry the burden: it doesn't explain what 'safe' means, what output to expect, or whether any other side effects 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 a single, direct sentence with no fluff. The core action and a key behavioral guarantee are front-loaded.

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

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

Despite being concise, the tool has nine optional parameters and no output schema. The description does not explain which parameter to use, what a safe path result means, or what shape the response takes, so it is not fully self-sufficient.

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 already describes all nine parameters individually, but the tool description only relates to 'path' and does not clarify how the other eight parameters (url, city, feed, etc.) fit into checking a path. This mismatch adds confusion rather than meaning 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 action and object: 'Check whether a path looks safe. No disk access.' It distinguishes itself from sibling URL or name checkers, though the meaning of 'safe' is left somewhat undefined.

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 instead of similar siblings like browser-url-ok, normalize-url, or wiki-title-ok. It also doesn't clarify which of the many optional parameters should be supplied.

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 Open-Meteo as a data source and provides no details about side effects, return format, or what happens with the other parameters. Since no annotations are present, the description carries the full transparency burden and fails to disclose that most parameters are described as 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 very brief and easy to read, but it omits essential structural information like which parameter is required or how parameters relate. It is concise but at the cost of being incomplete and ambiguous.

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 output schema, and no explanation of parameter relevance, the description is far from complete. An agent cannot determine what to pass, what to expect back, or how to handle the many apparently irrelevant parameters.

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

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

Although every parameter has a description, those descriptions are actively misleading—e.g., 'ref' says it is discarded after a shape check, and 'query' says it is discarded after a length check, none of which align with geocoding. The schema does not meaningfully clarify how to request latitude and longitude for a place.

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 that the tool returns latitude and longitude via Open-Meteo, but it does not specify what input to provide. With nine unrelated optional parameters and no mention of a 'place' parameter, an agent cannot confidently determine what this tool actually does.

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

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

There is no guidance on when to use this tool versus alternatives like weather-hint or timezone. It does not explain which parameter is the place name or what conditions would make it the right choice.

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 is the sole source. 'Parse' implies a read-only operation with no side effects, but this is not explicitly stated. The lack of detail about error handling or network access leaves some ambiguity, but the nature of parsing suggests low risk.

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 concise sentence with no redundancy or unnecessary detail. It is perfectly sized for the minimal information it conveys.

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 omits critical information: the expected input parameter (likely 'url'), the output format (owner and repo as separate fields or an object?), and error behavior for invalid URLs. Without these, a user cannot reliably use the tool without additional inspection.

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 explain any parameters, and the schema descriptions are generic or misleading (e.g., 'url' is described as 'HTTPS URL to normalize or cite' rather than for parsing owner/repo). The presence of many unrelated parameters (city, feed, path, etc.) is confusing, and the description offers no clarification about which parameter is relevant.

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

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

The description clearly states a specific action ('Parse owner and repo') and a specific resource ('GitHub URL'), making the purpose understandable. It does not explicitly differentiate from sibling shape tools, but the mention of GitHub distinguishes it.

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 vs alternatives, nor any mention of context or conditions. The description only states what it does, leaving the user to infer appropriate usage.

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 implies a read-only counting operation, but it does not disclose side effects, network access, or how parameters are handled, especially since the schema includes unrelated fields with 'discarded' notes.

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 and to the point, but the phrase 'Titles discarded' is cryptic and could be clearer without adding 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?

The description omits essential context about parameter usage, output format, and why unrelated parameters are present, making it impossible to invoke correctly based on the definition alone.

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 disconnected from the stated purpose (e.g., 'city', 'json', 'path'). None of the parameter descriptions explain how they contribute to counting Hacker News stories, so they add no meaningful guidance.

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 and object ('Count current Hacker News front-page stories'), but the phrase 'Titles discarded' is ambiguous and the listed parameters are entirely unrelated to this purpose, undermining overall 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 given about when to use this tool versus alternatives, and the mismatch between the description and the parameter schema leaves the agent without any usage direction.

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

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

With no annotations provided, the description must carry the burden of explaining behavior, but it does not mention return format, side effects, or how the nine input properties relate to the tool. The schema's property descriptions mention shape checks, normalization, and discarded values, none of which are reflected in the tool description.

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

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

The description is a single short sentence with no filler or redundant wording. It is appropriately concise for the limited information it provides.

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?

Despite a nine-property input schema and no annotations or output schema, the description gives almost no contextual information. An agent cannot tell what the parameters mean for this tool, what output to expect, or how the tool fits into a broader workflow.

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 a 3 even without parameter details in the tool description. The description adds only minimal context by saying 'common' and 'for clock calls' for the zone field, but it does not clarify the many unrelated optional 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 phrase 'Common IANA timezone names for clock calls' conveys a general purpose, but it is a noun phrase without an explicit verb like 'list' or 'get.' An agent can infer the intended function, but the lack of a clear action makes the purpose somewhat vague.

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 related sibling tools such as timezone or utc-time. The description only says 'for clock calls' without explaining prerequisites, alternatives, or preferred invocation contexts.

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, but it only mentions fetching and counting groups. It does not disclose side effects, failure modes, rate limits, or data handling 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 main description is a single concise sentence, which is appropriately brief. However, the surrounding parameter list is long and mismatched, making the overall tool definition feel disjointed rather than well-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?

The definition lacks an output schema, required parameters, examples, or explanation of how the supplied parameters relate to the tool's purpose. An agent would not know what 'group counts' means or how to invoke 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?

Although every parameter has a schema description, those descriptions are generic and largely unrelated to robots.txt, such as 'Git ref name' and 'City name for a public weather hint'. They do not clarify how parameters map to fetching robots.txt or counting groups.

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 only group counts, giving a specific action and resource. However, it does not specify which parameter supplies the URL, leaving minor ambiguity.

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

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

No guidance is provided about when to use this tool versus alternatives, nor any context about expected inputs or selection criteria. The description only states what it does, not when it should be used.

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 'Key discarded', indicating the input is not retained, but there is no mention of side effects, errors, read-only guarantees, or network/disk access. With no annotations, this 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 extremely short and front-loaded, but the brevity comes at the expense of essential information. It omits how the many parameters relate to the tool and what output is expected.

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 output schema, and no annotations, the description is far too incomplete. It fails to explain which parameter is the Jira key, what constitutes a valid shape, what the tool returns, or how errors are reported.

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 disconnected from the tool's stated purpose. For example, 'url' is described as 'HTTPS URL to normalize or cite' and 'city' as 'City name for a public weather hint', which do not relate to checking a Jira key shape.

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 a Jira issue key shape'), but the input schema contains nine unrelated optional parameters with no indication of which one holds the Jira key or what 'shape' means in this context.

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, what prerequisites exist, or how it differs from sibling shape-checking tools like github-repo-shape or figma-url-shape.

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 gives no indication of side effects, return values, errors, or validation behavior. The agent has no way to predict what happens when the tool is 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 a single vague sentence with no structure, no examples, and no elaboration. It is concise in word count but entirely insufficient to convey 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?

There is no output schema, no parameter guidance tied to the tool purpose, and no behavioral detail. The tool cannot be used correctly based solely on the provided description and schema.

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 type and a short description, but the descriptions seem disconnected from the stated language-tag purpose and often mention only incidental effects (e.g., 'discarded after the shape check'). The schema provides some structural clarity, but does not explain how parameters relate 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 'ISO 639 language tag gu.' does not state what action the tool performs, what it returns, or what inputs are expected. It reads more like a fragment or label than an explanation, leaving the tool's purpose entirely 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 any sibling tool. It does not mention scenarios, limitations, or prerequisites, so an agent cannot determine appropriate invocation 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?

There are no annotations, and the description does not explain side effects, error behavior, network access, or what 'Body discarded' means operationally. The input descriptions saying parameters are 'discarded' further obscure the tool's behavior.

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

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

The description is short but not effective; it omits crucial context while including confusing, irrelevant phrases. The parameter descriptions add noise rather than clarity, making the overall structure unhelpful.

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, required parameters, and any explanation of what the HTTP status refers to. Given the nine heterogeneous parameters and no annotations, the description is far from complete enough for an agent to use safely.

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, most descriptions state the value is 'discarded' or are unrelated to the stated purpose. The connection between parameters like 'city', 'zone', or 'json' and 'HTTP status for a public library docs URL' is entirely unclear.

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 'HTTP status for a public library docs URL. Body discarded.' is ambiguous and does not clearly state what the tool actually does. The name 'lib-docs-hint' and the unrelated parameter descriptions further obscure the intended purpose.

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

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

No guidance is provided on when to use this tool versus alternatives like fetch-status, browser-url-ok, or web-fetch. The description does not mention use cases, prerequisites, or distinguishing characteristics.

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 behavioral disclosure; it states that values are discarded, but does not mention output format, invalid JSON handling, or whether nested keys are counted. 'Discarded' is also potentially misleading about 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 short sentences with no filler or redundant 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?

For a tool with 9 optional parameters and no output schema or annotations, the description lacks essential context such as which parameter to populate, the return format, and edge-case behavior. It states the core purpose but is not complete enough 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?

Although every parameter has a schema description, the tool description does not indicate which parameter holds the JSON object, and the 'json' parameter's schema description says 'JSON text to validate; discarded after the check', which contradicts the counting purpose. The other parameters are unrelated and all are optional, leaving the agent without actionable parameter guidance.

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 keys in a JSON object and ignores values, which is a specific verb and resource. However, it does not explicitly tie this to the 'json' input parameter, so there is slight ambiguity.

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

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

The description gives no guidance on when to use this tool instead of related siblings like validate-json or search-query-len. The purpose implies a key-counting use case, but no explicit when/when-not conditions 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 explaining side effects, errors, and output shape; it only mentions dropping query and fragment. The schema descriptions of unrelated params being 'discarded' add confusion rather than transparency.

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 prose is concise and front-loaded, with no fluff; both sentences earn their place. However, the overall tool definition is bloated by nine optional parameters that are not reflected in the description.

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

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

Given nine optional parameters, no required parameters, no output schema, and no annotations, the description is far too incomplete to understand how to invoke the tool correctly or what it returns. It does not explain the purpose of the unrelated parameters or the output structure.

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, most are irrelevant to URL normalization (e.g., 'Git ref name', 'City name for a public weather hint', 'JSON text to validate') and provide misleading semantics. The only relevant parameter, 'url', is described vaguely 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 clearly states the tool returns origin, host, and path for a URL and explicitly says query and fragment are dropped. It does not explicitly contrast with sibling URL-related tools, but the core purpose is specific 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?

There is no guidance about when to use this tool instead of alternatives such as web-fetch or URL-shape tools, nor any indication of what inputs are expected beyond the one URL.

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

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

The description discloses that no browser is launched, a key behavioral trait. However, it does not mention other potential side effects such as network requests, timeouts, or whether it performs a HEAD vs GET request. With no annotations, this partial disclosure is insufficient for full transparency.

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 that conveys the core functionality and a key differentiator. No unnecessary words or redundant information.

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

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

The description is extremely incomplete for a tool with 9 parameters and no output schema. It does not explain what input the tool expects, how to use it, what output it returns (e.g., boolean, status code), or how the extraneous parameters are handled. An agent cannot reliably invoke this tool based on the given information.

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 parameters, all optional and with descriptions that are unrelated to the tool's purpose (e.g., 'city', 'feed', 'zone'). The 'url' parameter description says 'normalize or cite' which does not match 'check if can be opened'. The tool description provides no parameter context, leaving the schema misleading and 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 description clearly states the tool checks whether a URL can be opened, and the note 'No browser is launched' differentiates it from browser-based siblings like 'browser-url-ok'. However, it does not explicitly mention the required input parameter (URL), which slightly reduces 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?

The description implies usage without launching a browser but does not explicitly state when to prefer this tool over alternatives like 'browser-url-ok' or 'fetch-status'. Guidance on when not to use it is absent.

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 that the query is discarded, providing some transparency about side effects. However, it does not mention whether other parameters are also ignored or if any state is modified, and with no annotations provided, the description carries the full burden but only partially fulfills it.

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, clear sentence. It is concise, contains no redundancy, and is well-structured, 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 description omits important context: it does not explain the role of the many other parameters in the schema, nor does it specify the return value or behavior for empty or missing queries. Given the tool's simplicity, this leaves gaps in understanding how to invoke it correctly.

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

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

The schema describes 100% of parameters, so the baseline is 3. The description adds no additional meaning to the parameters themselves; it only references the query parameter. The schema descriptions are sufficient, but the description does not enhance understanding beyond that.

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

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

The description clearly states the tool counts characters in a search query, which is a specific action. However, it does not explicitly distinguish itself from sibling tools, though no sibling appears to perform character counting, so it is functionally unique.

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

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention any related tools or conditions under which this tool would be preferred, leaving the agent without direction for selection.

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

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

No annotations are present, so the description carries the full burden of disclosing side effects, permissions, or data handling. The description does not mention any behavioral aspects (e.g., whether it performs network calls, writes data, or only reads). The parameter descriptions mention 'discarded' but that refers to parameter handling, not tool behavior.

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

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

The description is extremely concise—a single short sentence with no filler words. It gets straight to the point, though the point itself is vague. No unnecessary information is included.

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 any output schema, annotations, or explanatory details. The description is insufficient to understand how to invoke the tool, what the expected output is, or how the parameters relate to the purpose. Given the mismatch between the description and the parameter set, the description is not adequate for an agent to use 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 parameter descriptions are individually provided but do not connect to the tool's stated purpose of being an HTTP status code catalog. For example, 'ref' is described as a Git ref name, 'city' as a city name, and 'query' as search text—none of these relate to HTTP status codes. The schema coverage is 100% in that every parameter has a description, but the descriptions do not clarify how these inputs are used or why they matter 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 states a purpose ('Short catalog of common HTTP status codes') but does not specify the actual action (e.g., list, lookup, validate). It is a noun phrase rather than a verb-driven tool description. The extensive parameter list (ref, url, city, feed, host, json, path, zone, query) does not align with the stated purpose, creating confusion about 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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of conditions, edge cases, or comparisons to sibling tools. The description is entirely silent on 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, but it does not disclose side effects, read-only behavior, error cases, or what happens to inputs. Phrases like 'discarded after the shape check' hint at validation but never explain the actual 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 short and front-loaded, with no redundant filler. But the single vague sentence sacrifices clarity for brevity, and the parameter descriptions are internally inconsistent with the top-level description.

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

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

There is no output schema or return-value explanation, no required-parameter context, and no description of how the 9 optional parameters relate to the stated 'thinking template'. An agent cannot tell what the tool will do or what to expect in 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 9 parameters have descriptions, and each one names a domain concept (Git ref, URL, city, feed, host, JSON, path, timezone, search text). However, the repeated 'discarded' wording obscures how the parameters are used and what result is produced.

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 'Return a three-step thinking template' but does not specify what resource or action it operates on, and 'Prompt discarded' is confusing. It does not distinguish this tool from sibling validators like validate-json 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?

No guidance is provided for when to use this tool instead of any of the 26 sibling tools. The description does not state prerequisites, typical use cases, or conditions under which it 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?

There are no annotations and the description does not disclose any behavior, such as error handling for invalid zone names, whether it reads the system clock, or whether it makes network calls. The tool's operational characteristics are 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, compact sentence with no fluff or redundancy, achieving maximum conciseness while conveying the core 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?

The description is far too sparse to be complete given the large, noisy schema and the presence of many sibling tools. It omits the key relationship between the tool and the 'zone' parameter, does not mention what output to expect, and provides no context about alternatives or edge cases.

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 lists 9 parameters, but the description never mentions which one (zone) is the meaningful input. Several parameters (ref, url, city, feed, host, json, path, query) are described as 'discarded after the shape check' but there is no explanation that they are irrelevant. An agent could easily pass the wrong parameter or be confused by the extraneous fields.

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

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

The description clearly states the tool returns the current time in a named IANA timezone, which is a specific action and resource. It distinguishes itself from the sibling utc-time (which gives UTC) and iana-zones (which lists zones) by specifying 'named IANA timezone'.

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

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

The description provides no guidance on when to use this tool instead of alternatives like utc-time or geo-hint, nor does it indicate any prerequisites or typical use cases. An agent gets no direction on selecting 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 does not disclose that all input parameters are ignored during execution, nor does it mention side effects or read-only nature. The presence of unrelated parameters without explanation obscures the tool's actual 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 extremely concise, consisting of a single phrase, and is well-structured with no unnecessary words.

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

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

The description is incomplete because it does not explain why the input schema contains unrelated parameters or that they are ignored. This contextual gap could mislead 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?

All nine parameters have descriptions that are unrelated to UTC time and suggest other purposes (e.g., 'Git ref name', 'URL', 'city'). The descriptions imply these are used for shape or length checks, but the tool description does not explain their role, leading to confusion.

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

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

The description clearly states the tool returns the current UTC timestamp, which is unambiguous and distinguishes it from timezone-related tools. However, it lacks an explicit verb like 'Get'.

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 instead of alternatives like 'timezone' or 'fetch-status'. The description gives no context for selection.

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 discloses that the body is discarded, which is a useful side-effect note, but it does not describe return values, error behavior, or whether validation is strict/lenient. With no annotations provided, critical behavioral information is missing.

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, direct, and front-loaded: it immediately states the action and the disposal behavior. It contains no filler or redundant wording, though it could be slightly more explicit about inputs/outputs.

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 that there is no output schema and no required parameters, the description is not complete enough for an agent to reliably use the tool. It does not specify what a successful or failed validation looks like, nor how to pass the JSON body given the broad set of optional parameters.

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

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

Although every parameter has a schema description and the 'json' parameter is relevant ('JSON text to validate'), most other parameters are unrelated to validating JSON, and their descriptions (e.g., 'Git ref name; discarded after the shape check') do not clarify how they relate to the tool's purpose. This makes parameter usage 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 description states that the tool checks whether a body is valid JSON and that the body is discarded, which conveys a clear core purpose. However, 'body' is ambiguous and the input schema contains many unrelated parameters (ref, url, city, feed, host, path, zone, query), so an agent cannot determine what input actually represents the JSON body.

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

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

The description implies a validation use case but does not explain when to choose this tool over sibling validation tools, how the JSON body should be supplied, or what the expected output is. There is no guidance on alternatives or conditions under which this tool should or should not be used.

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 discloses that Open-Meteo is used, but it does not explain side effects, persistence, network behavior, or error handling. With no annotations available, this leaves significant behavioral ambiguity.

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

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

The description is one short sentence with no unnecessary words. It is concise and front-loaded, stating the core function immediately.

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 mention output format, temperature units, error cases, or required parameters. With no output schema and no annotations, an agent cannot predict the response, and the nine optional parameters add further 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?

The schema provides descriptions for all parameters, so the baseline is met. However, the tool description itself only mentions city, and several parameter descriptions are confusing or seemingly unrelated to weather, so the parameter semantics remain unclear.

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

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

The description clearly identifies the tool as returning current temperature for a city via Open-Meteo, so the core purpose is understandable. It is not phrased with an explicit verb like 'get', but the intent is unambiguous. The unrelated optional parameters slightly cloud the purpose but do not hide it.

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 indication of when to use this tool over alternatives or when not to use it. The only implied context is that it is for weather lookups, but no explicit usage guidance is 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?

The description discloses one important behavior: the response body is discarded and only HTTP status and content type are returned. With no annotations to carry the burden, it omits other behavioral details such as error handling, redirects, network failures, and the apparent no-op behavior of the many extra parameters described as '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 very concise and contains no filler, with one sentence for the core behavior and one for the body-discarding constraint. It could be improved by using an explicit verb and a clearer sentence structure, but it is not padded or overly verbose.

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 the actual schema: it only addresses the URL parameter and ignores the eight other parameters, their apparent validation/discard behavior, and any output format details. There is no output schema, so the description should have explained more about what a successful response contains beyond 'HTTP status and content type'.

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 (100% coverage), most descriptions are unrelated to the stated web-fetch purpose and suggest that values are ignored or used only for shape checks, e.g., 'discarded after the shape check' and 'no disk access'. The url parameter itself is described as 'HTTPS URL to normalize or cite', which conflicts with fetching HTTP status and content type, so the parameter descriptions are misleading despite high coverage.

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 core output as HTTP status and content type for a public URL and notes the body is discarded. However, it lacks an explicit verb and does not differentiate this from sibling status-check tools such as fetch-status or browser-url-ok, especially because the input schema includes many unrelated optional parameters.

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

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

The description provides no explicit guidance about when to use this tool instead of the many sibling tools, such as fetch-status, normalize-url, or browser-url-ok. The only implied constraint is that the body is not fetched, so it should not be used when full page content is needed.

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 'Title discarded after the call,' which hints at statelessness but is vague and does not clarify whether the tool makes network requests, returns a boolean, or has other side effects. With no annotations, the description carries the full transparency burden and falls short.

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 the second sentence 'Title discarded after the call' is confusing and does not clarify the tool's behavior. It is concise but at the cost of essential information.

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

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

The description and schema together do not provide enough context to invoke the tool correctly. There is no output schema, no mention of return values or error behavior, and no explanation of which parameter, if any, should be used for the title.

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

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

The schema descriptions are entirely mismatched with the tool's stated purpose. None of the parameters (ref, url, city, feed, host, json, path, zone, query) corresponds to a Wikipedia title, and the inline descriptions reference unrelated concepts like Git refs, URLs, weather hints, and JSON validation.

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 Wikipedia title exists'), but it does not identify any input parameter that carries the title. The schema contains nine unrelated properties, so an agent cannot determine how to specify the title.

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 fetch-status, normalize-url, or search-query-len. The intended use case is implied by the name and description, but not explicitly contrasted with sibling tools.

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