ISO country AI

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

With no annotations, the description must disclose behavior, but it only says 'Expression discarded'—an irrelevant note since no expression parameter exists. It does not explain how the provided parameters are processed, what side effects occur, or what the tool actually does with the input. This is a significant transparency gap.

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

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

The description is extremely short (one sentence), so it is technically concise in length, but it fails to earn its place because it provides incorrect and incomplete information. The brevity is not a virtue here; it is a symptom of under-specification.

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

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

The tool has 9 parameters, no annotations, no output schema, and a description that does not match the schema at all. An agent has no idea what the tool does, what the parameters mean in context, or what the expected result is. This is a completely inadequate definition for such a complex 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 schema coverage is 100%, the description adds zero value to parameter understanding and actually contradicts the schema by referencing 'a+b' when no such parameters exist. For all 9 parameters, the schema descriptions are the only source of meaning, and the tool description misleads about their role. This warrants a score well below the baseline.

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

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

The description claims to evaluate 'a+b style arithmetic', but the input schema contains 9 unrelated parameters (ref, url, city, feed, host, json, path, zone, query), none of which represent an arithmetic expression or operands. The purpose is not just vague—it is actively misleading, as the schema suggests a completely different tool. There is no differentiation from siblings either.

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 28 siblings. The description gives no context about which scenarios warrant calling calc-eval, and its misleading purpose makes it impossible 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?

No annotations are provided, so the description carries the full burden. It only states that the tool does not include WHOIS or ownership data, which is a limited behavioral disclosure. It does not mention that only the 'host' parameter is used, that other parameters are discarded, or whether any network or disk access occurs. The schema descriptions mention 'discarded after the shape check' for several parameters, but this is not reflected in the tool description, leaving the agent unaware of side effects or output characteristics.

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 is front-loaded with the primary purpose. However, it omits essential context about the parameter set and usage constraints, making it under-specified rather than appropriately concise. It earns a middle score because it is efficient but incomplete.

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 parameters, no output schema, and no annotations, the description is significantly incomplete. It does not explain what the tool does with all parameters, what the output format is, or how an agent should construct a valid call. The tool appears to be a multi-purpose shape checker, but the description narrows it to hostname splitting, leaving the agent without enough information to use it correctly for other parameter types.

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 minimal value beyond that; it reinforces that 'host' is a public hostname but does not clarify the role of the other eight parameters or that they are effectively ignored. With complete schema coverage, the baseline of 3 is appropriate, but the description fails to help the agent understand which parameter to actually supply.

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 a clear resource (hostname). However, the input schema includes nine parameters (ref, url, city, feed, json, path, zone, query) that are not addressed by the description, making the tool's actual scope ambiguous and failing to distinguish it from siblings like figma-url-shape or github-repo-shape. The core purpose is clear but incomplete.

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, nor does it explain which of the nine parameters is relevant. The description implies hostname input but does not explicitly state that other parameters are ignored or how to select this tool over domain-related siblings. This leaves the agent without clear decision criteria.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool uses HEAD and returns status, but does not disclose that it also validates other inputs (e.g., JSON, timezone, path) or that many parameters are discarded after shape checks. The description is incomplete and potentially confusing, as it hides the tool's broader behavior.

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

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

The description is a single, front-loaded sentence with no waste. However, it is so concise that it omits critical context about the tool's other capabilities. It is not verbose, but it is under-specified for the tool's complexity, so it earns a middle score for structure.

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 parameters, no annotations, and no output schema, the description is woefully incomplete. It explains only the URL HEAD behavior, leaving the agent unaware that the tool can also validate JSON, check timezones, or perform shape checks on paths and hostnames. An agent would not know how to invoke the tool for any purpose other than URL status checking.

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

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

Schema coverage is 100%, so the baseline is 3, but the description actively misleads parameter usage by focusing only on URL. It does not clarify that the other parameters trigger different checks. While the schema descriptions are helpful, the tool description contradicts them by implying only a URL is relevant, making it harder for an agent to know which parameter to supply.

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 resource ('HEAD a public URL and return status only'), which distinguishes it from sibling URL tools like web-fetch or browser-url-ok. However, it is misleading because the schema accepts nine diverse parameters (ref, city, json, path, zone, etc.), many of which are unrelated to URLs. The description fails to convey the tool's actual multi-purpose nature, so an agent would mis-scope its capabilities.

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. It does not mention sibling tools such as web-fetch, validate-json, or timezone, nor does it explain which parameter to use for which scenario. The description implies only URL status checking, leaving the agent without any basis for selecting it for non-URL 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 carries the full burden of behavioral disclosure. It only states that the tool returns lat/lon for a place, but does not disclose that many input parameters are discarded, whether the call is read-only, involves network requests, or what side effects occur. The schema hints at discarding parameters but the tool description omits this entirely.

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 core function. However, it is too brief given the complexity of the schema and does not structure information about parameter usage or behavior. It is efficient but under-specified, so a score of 4 is appropriate.

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, no annotations, and no output schema, the description is severely incomplete. It does not explain the return format, which parameters are relevant, or how to handle the seemingly unrelated fields. The tool cannot be called correctly based on the description 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 schema coverage is 100%, the descriptions of the parameters do not align with the tool's stated purpose. For example, 'city' is described as for a 'public weather hint' and 'discarded after the call', which conflicts with geocoding. The description adds no clarity about which parameter to use for the place, making it hard for an agent to select the correct input.

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

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

The description states a clear primary function: providing latitude/longitude via Open-Meteo. However, the input schema contains nine parameters, many of which (ref, url, feed, host, json, path, zone, query) seem unrelated to geocoding, creating ambiguity about what the tool actually does. The description does not address this mismatch, so the purpose is only partially clear.

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

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

There is no guidance on when to use this tool versus alternatives like weather-hint, timezone, or iana-zones. No conditions, prerequisites, or exclusions are mentioned. The agent is left to infer usage from the schema, which is confusing given the unrelated parameters.

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

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says it parses owner and repo, but does not mention error handling, return format, side effects, or the fact that other parameters are discarded. The schema hints at validation behaviors (e.g., 'discarded after the shape check'), but the description omits these entirely. This is a serious gap for a tool with no annotations.

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 at one sentence, but it is under-specified relative to the complexity of the schema. While it front-loads the primary purpose, it omits any mention of the additional parameters or their purpose, making the structure appear incomplete rather than efficiently minimal. The sentence earns its place but does not adequately structure the tool's 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?

With nine parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the return value, how to handle errors, or how the non-url parameters interact with the parsing logic. An agent would be unable to confidently invoke this tool for anything beyond a simple GitHub URL, and the presence of unrelated parameters would likely lead to misuse.

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

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

Schema coverage is 100%, so each parameter has a description, but the tool description does not add any extra meaning. It does not clarify how the url parameter is used or why the other eight parameters exist. The description's mention of only 'URL' fails to explain the role of parameters like 'ref', 'city', or 'json', leaving the agent without a coherent model of how to invoke the tool correctly.

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

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

The description clearly states a specific verb ('parse') and resource ('owner and repo from a GitHub URL'), which distinguishes it from siblings like 'normalize-url' or 'figma-url-shape'. However, the schema exposes nine unrelated parameters (city, feed, json, etc.) that the description does not account for, creating ambiguity about the tool's true scope. The core purpose is clear, but the schema undermines it slightly.

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. The description only states what it does, without mentioning when it is appropriate or when another tool (e.g., 'normalize-url' for generic URLs) should be preferred. An agent would have to infer usage from the name and 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?

With no annotations, the description carries the full burden of behavioral disclosure. It only says the tool counts stories and discards titles, but does not explain side effects, network usage, parameter handling, or return format. It also does not clarify that the tool performs only local shape validation (as implied by the schema) rather than live fetching. This is a significant gap 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, so it is concise, but it is under-specified. It front-loads the main purpose but omits critical details such as input expectations and return value. The brevity is not balanced with completeness, making it less effective than a slightly longer but more informative 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 the tool has 9 optional parameters, no output schema, and no annotations, the description is extremely incomplete. It does not explain what the tool returns (e.g., a number), what the parameters are for, or whether it performs any network calls. The agent cannot reliably invoke this tool based on the provided information, especially because the parameters seem unrelated to the stated 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 schema provides 100% coverage with each parameter described (e.g., 'discarded after the shape check'). However, the tool description adds no extra meaning about how these parameters relate to counting HN stories. The parameters seem unrelated to the stated purpose, creating confusion. Since the schema already explains each parameter, the baseline is 3, but the description does not resolve the mismatch.

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 resource: 'Count current Hacker News front-page stories.' This distinguishes it from most siblings, which focus on URL validation or time/weather. However, the phrase 'Titles discarded' is ambiguous and does not clarify whether the tool returns a count only or processes input shapes. It is not a tautology and has a concrete action.

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 prerequisites, exclusions, or related tools. For a tool that appears to be a shape-checker (based on the schema and siblings), it fails to clarify that it validates inputs rather than actually fetching HN data, leaving the agent uncertain about its role.

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 behavioral disclosure burden. It reveals that the body is discarded, but does not disclose that only the 'url' parameter is meaningful while the other eight parameters appear to be ignored or unrelated. The wide array of parameters (city, feed, json, zone, etc.) contradicts the narrow 'public library docs URL' scope, and this mismatch is left unexplained. No side effects, authentication needs, or rate limits are mentioned.

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 is concise and front-loaded with the core purpose. It avoids fluff and gets straight to the point. However, it omits essential details, but conciseness is about length and structure, not completeness, so a 4 is appropriate.

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 9 parameters, no output schema, and no annotations, the description is markedly incomplete. It does not specify which parameter is the target URL, how the other parameters are handled, or what the exact return value looks like (beyond 'HTTP status'). An agent would struggle to call this tool correctly, especially with the seemingly unrelated 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter-level meaning; it does not even indicate which parameter is the URL or that other parameters are disregarded. The schema descriptions themselves are informative, but the tool description offers no additional clarification, leaving the agent to infer that 'url' is primary based on the prose.

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 and resource: 'HTTP status for a public library docs URL.' It is a distinct verb-resource pair. However, it does not differentiate from sibling tools like fetch-status or browser-url-ok, which also report HTTP status. The name 'lib-docs-hint' suggests a hint rather than a direct status, but the description is 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 given on when to use this tool versus alternatives. The description only states what it does, with no mention of conditions, exclusions, or preferred scenarios. An agent cannot decide between this and sibling HTTP-check tools based on this description.

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 'Query discarded,' which is a useful trait, but it does not disclose what happens to the other parameters, whether any network access occurs, or what the output format is. The schema mentions 'discarded after the shape check' for some fields, but that is not in the description, leaving the tool's full behavior opaque.

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

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

The description is extremely concise (two short sentences) and front-loads the primary action. However, its brevity omits critical context about the other parameters, so while it is concise, it is not optimally 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?

For a tool with 9 parameters and no output schema, the description is severely incomplete. It does not explain the purpose of the other parameters, the relationship between them, or what the return value is. An agent cannot reliably understand how to call this tool correctly 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 schema description coverage is 100%, so each parameter is documented in the schema. The description adds no extra semantic meaning beyond restating that the query is discarded, which is already in the schema. The baseline of 3 is appropriate because the schema carries the semantic burden.

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 ('Count characters in a search query') and a clear resource, but the input schema contains 9 diverse parameters (ref, url, city, feed, etc.) that the description does not address, making the tool's actual scope ambiguous. It does not differentiate this tool from sibling shape-check tools like domain-shape 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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of conditions, exclusions, or alternative tools. The agent is left to infer usage from the name and schema.

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

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

No annotations are provided, so the description must carry the behavioral burden. It simply says 'Current UTC timestamp' without disclosing how parameters affect the call, whether there are side effects, or what happens with the nine optional inputs. The parameter descriptions hint at validation or discarding, but the description does not clarify the actual behavior, leaving 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 a single sentence, which is concise and front-loaded. However, it is under-specified for a tool with nine parameters and no output schema. It earns a middle score because it is not verbose, but it lacks substance.

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

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

The tool has nine optional parameters, no output schema, and no annotations. The description only states the output (current UTC timestamp) without explaining the purpose of the parameters, the output format, or any limitations. An agent would be confused about why these parameters exist and how to use them. The description is inadequate for the tool's complexity.

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. The tool description adds no additional meaning beyond the schema. Given high coverage, the baseline of 3 applies. The parameter descriptions themselves are odd (e.g., 'discarded after the shape check'), but that is part of the schema, not the tool description.

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

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

The description states a clear verb and resource: 'Current UTC timestamp.' It tells the agent exactly what the tool returns. However, it does not differentiate from sibling tools like 'timezone' or 'iana-zones,' which also deal with time. So it's clear in purpose but lacks sibling differentiation.

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

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

There is no guidance on when to use this tool versus alternatives. No mention of contexts, exclusions, or when to prefer other tools. The description only states what it does, leaving the agent to infer 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?

With no annotations, the description carries the full burden. It discloses that the body is discarded and that the output is status and content type, but it does not explain the behavior for the 9 optional parameters, most of which are marked as 'discarded after the shape check' in the schema. There is no mention of authentication, rate limits, or error handling.

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 sentence with no filler. However, it is almost too brief, omitting essential context about parameter behavior. The brevity is good, but the structure lacks detail that would aid 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?

For a tool with 9 optional parameters and no output schema, the description is severely incomplete. It does not explain the purpose of the non-URL parameters, the relationship between them, or what the tool actually does with them. The agent cannot determine how to invoke it correctly for anything beyond a simple URL fetch.

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

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

Schema description coverage is 100%, so the schema already documents each parameter. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate. It does not clarify how the URL parameter relates to the other parameters or how they interact.

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: fetching a public URL and returning HTTP status and content type, with body discarded. This is a specific verb+resource. However, it does not distinguish itself from sibling tools like fetch-status or browser-url-ok, which likely serve similar purposes, so it lacks differentiation.

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. The description does not mention any conditions, exclusions, or alternative tool names, leaving the agent to guess which of the many sibling tools to pick.

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 mentions 'Title discarded after the call' but since no title parameter exists, this is confusing. It does not disclose return values, side effects, or any other behavioral 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 concise at two sentences, but the second sentence is odd and does not add useful information. It is under-specified for a tool with this many parameters.

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

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

For a tool with 9 parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain what the tool returns, how to input a title, or any prerequisites, making it nearly impossible to use 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 does not explain any parameters. The schema has 9 parameters with descriptions, but none are linked to a Wikipedia title, and the description does not clarify which parameter to use. Despite 100% schema coverage, the description adds no value and introduces ambiguity about how to specify the title.

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: 'Check whether a Wikipedia title exists.' However, the schema contains no parameter for a title, and the listed parameters (ref, url, city, etc.) are unrelated, creating confusion about what to pass. It does not differentiate from siblings beyond the resource name.

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

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

The description provides no guidance on when to use this tool versus alternatives. There is no mention of conditions, prerequisites, or exclusions, leaving the agent to guess.

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