Language fj

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

No annotations are present, and the description discloses almost nothing about side effects, network access, latency, errors, or data handling. The parameter descriptions say values are 'discarded' or 'checked,' but the overall behavior remains 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 text is short, but it is cryptic and structurally confusing. The sentence 'Task text discarded' appears without context, and the description mixes unrelated concepts ('weather, search, scrape, or voice') with no clear organization.

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 examples, no error behavior, and no relationship to the sibling tools. The description is not enough for an agent to understand what this tool is for or how to invoke it successfully.

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 performative rather than meaningful: 'query' is 'Search text; discarded after the length check' and 'city' is 'City name for a public weather hint; discarded after the call.' No parameter is required and there is no explanation of how any of them relate to the so-called task or gateway.

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

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

The description names an action ('find') and a resource ('public pay-per-call tool gateway'), but the intended behavior is unclear: 'for a task such as weather, search, scrape, or voice' is vague, and the parameter list is a disconnected grab bag. The phrase 'Returns connection methods' does not clarify what the tool actually outputs.

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 compared to the many sibling tools. No conditions, examples, or selection criteria are provided, and the description does not explain how a caller should choose among the nine optional 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?

The description discloses that no browser is launched, but it does not explain what 'ok' means, what side effects or network effects may occur, what failure modes exist, or what the return value looks like. Since there are no annotations and no output schema, the description carries the full transparency burden and does not meet 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 short and front-loaded with the core action, but it omits necessary structural detail such as return format, error behavior, and parameter relevance. It is concise in word count but not well-formed as a functional tool 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 input schema has nine parameters and no output schema, the description is severely incomplete. It does not clarify which parameters are required or meaningful, what the tool returns, how success is determined, or how this tool relates to nearby siblings such as fetch-status and playwright-url-ok.

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 contains nine parameters, but only url is plausibly relevant to checking whether a URL can be opened, and even its description says to normalize or cite it rather than open it. The other eight parameters—ref, city, feed, json, path, zone, query—are unrelated and described as discarded or checked for shape, creating severe semantic noise and misleading an agent.

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 single action—check whether a URL can be opened—but leaves 'can be opened' undefined in terms of HTTP status, reachability, or browser compatibility. It also conflicts with the url parameter description, which says the URL is 'to normalize or cite' rather than to open.

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 only usage guidance is 'No browser is launched,' which is a constraint rather than guidance on when to use this tool versus sibling tools like fetch-status, normalize-url, or playwright-url-ok. There is no mention of appropriate contexts, prerequisites, or expected caller intent.

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 says the expression is discarded but no expression parameter exists, making the note confusing. No side effects, permissions, or other behavioral details are disclosed, and no annotations are present to fill the 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 very short and front-loaded, but it omits essential information and is inconsistent with the schema. Conciseness is achieved at the expense of clarity and utility.

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 is not complete for its stated purpose: there is no way to supply an arithmetic expression, no output schema, and no clarification of how the unrelated parameters relate to evaluation. A caller cannot reliably infer 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, the descriptions are unrelated to arithmetic evaluation (e.g., Git ref, URL, city name). The critical expression parameter is missing entirely, so the schema adds no meaningful guidance for the stated purpose.

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

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

The description states it evaluates a+b style arithmetic, but the schema has no expression parameter and instead lists nine unrelated parameters. This makes the tool's actual purpose ambiguous and potentially misleading.

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 any alternatives. Sibling tools are not referenced, and no conditions or recommended contexts are given.

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

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

No annotations are present, and the description gives only the terse behavioral hint 'Path discarded' without explaining side effects, return value, or error behavior. This is insufficient for an agent to understand the tool's full 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 one-sentence description is extremely concise, but it omits critical information about parameters and output. Brevity is achieved at the expense of usefulness, so it is not well balanced.

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

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

With no output schema and no explanation of how the nine heterogeneous parameters are used, an agent cannot reliably predict the tool's behavior or response. The description is far too incomplete for the tool's apparent 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?

Although every parameter has a schema description, those descriptions are generic boilerplate (e.g., 'City name for a public weather hint') and do not relate to parsing a Figma URL. The description adds no clarifying semantics for how these nine heterogeneous parameters are used.

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?

Clearly states it parses a Figma file URL and discards the path, distinguishing it from normalize-url or browser-url-ok by resource. However, it does not describe what 'shape' the output takes, leaving some ambiguity.

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

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

No guidance is given on when to use this tool instead of sibling tools like normalize-url or browser-url-ok. The name implies a shape-checking role, but the description does not make the selection criteria explicit.

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?

Mentions that no disk access occurs, but does not disclose return values, error behavior, or side effects; with no annotations supplied, this leaves most behavior unspecified.

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

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

Two short sentences deliver the core purpose and a key safety guarantee with no redundant wording.

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

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

The description is too sparse for the 9-parameter optional schema; it does not explain the role of the extra parameters, how to select inputs, or what a successful check returns.

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

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

Schema descriptions cover all parameters but many (ref, url, city, feed, host, json, zone, query) appear unrelated to the stated path-check purpose and are all optional with no explanation of when each should be used.

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?

Clearly states the action ('check') and target ('whether a path looks safe'), but does not differentiate from sibling tools such as normalize-url 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?

Provides no guidance on when to use this tool instead of alternatives; the only extra note ('No disk access') is a safety property, not 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 carries the full burden of disclosing behavior. It mentions the Open-Meteo source but does not state whether the tool is read-only, what inputs are required, or what errors/side effects may 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 sentence with no redundant wording, making it appropriately concise for the 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?

Given the complex 9-parameter schema and no output schema, the one-line description is not complete enough: it does not specify how to provide the place, what the response shape is, or what happens with the many 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?

Although all 9 parameters have schema descriptions, the description does not connect them to the geocoding purpose, and the schema mixes unrelated fields (ref, url, feed, host, json, path, zone) with optional city/query fields. This leaves ambiguity about which parameter actually specifies the 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 the tool returns latitude and longitude for a place using Open-Meteo, which is a concrete outcome and distinguishes it from weather-specific siblings. However, it does not specify the input parameter or output format, so it is not fully precise.

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 geo-hint over sibling tools such as weather-hint or timezone, nor does it mention any exclusions or alternatives. The intended use is only implied by the name and one-line purpose.

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

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

No annotations are provided, and the description does not disclose that all nine input parameters are ignored, what the return value looks like, or whether the tool performs network access. 'Titles discarded' is too vague to count as meaningful behavioral 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 brief and front-loaded with the main action. However, the second sentence 'Titles discarded' is ambiguous and could be clearer, though it does not introduce verbosity or structural problems.

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

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

There is no output schema and no explanation of the return format, error behavior, or the fact that all input parameters are ignored. Given the confusing nine-parameter schema, the description is not sufficient for an agent to confidently call the tool.

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

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

Although the schema has 100% description coverage, the parameter descriptions are unrelated to counting Hacker News stories and mostly say they are 'discarded after the shape check.' The description does not clarify why these parameters exist or whether any of them affect the result.

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 resource: 'Count current Hacker News front-page stories.' The phrase 'Titles discarded' is cryptic but does not obscure the core 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?

There is no guidance about when to use this tool versus any alternative, such as web-fetch or fetch-status. The description only states the action, leaving selection entirely to inference from the name.

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 exist, and the description only says 'Key discarded,' which is ambiguous. It does not reveal whether the tool returns a boolean, normalized value, or nothing, nor what side effects or errors 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 very short and free of fluff, but it omits essential information about the required input. Brevity here harms usability rather than enhancing it.

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 required parameters, and no explanation of how the nine optional fields relate to a Jira key, the tool is under-specified. An agent cannot call it confidently.

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, none of them describes or accepts a Jira issue key. Descriptions like 'Git ref name' and 'JSON text to validate' are unrelated and appear to be copied from other tools, so they do not compensate for the missing key parameter.

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

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

The description states a clear verb ('Check') and resource ('Jira issue key shape'), but it fails to specify which input parameter should contain the key. The schema offers nine unrelated optional strings and no 'key' field, so the purpose is not actionable.

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

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

No guidance is given for when to use this tool instead of sibling shape tools like github-repo-shape or domain-shape, nor what inputs are appropriate. An agent cannot decide between alternatives or know what to pass.

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 notes that the body is discarded, but does not explain side effects, what triggers errors, or how the parameters are used. The parameter descriptions are inconsistent with the stated purpose (e.g., 'city' for weather, 'zone' for timezone), indicating unclear 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 concise but contains minimal useful information. It is a single sentence that does not elaborate on the tool's functionality, making it insufficient despite its 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 or annotations, the description leaves critical information unspecified, such as what the tool returns (beyond 'body discarded'), how parameters affect behavior, and error conditions. The description is far from complete for an agent to use effectively.

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 covers 100% of parameters, the descriptions are misleading and do not align with the tool's stated purpose. For instance, 'url' is described as 'normalize or cite' while the tool is about HTTP status, and 'query' is about search text length. The descriptions do not help the agent understand parameter usage 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 'HTTP status for a public library docs URL' is vague and does not clarify what action is performed (e.g., check, fetch, validate). It fails to distinguish from sibling tools like fetch-status or url-ok, as it does not specify the exact nature of the status check or how it relates to the diverse 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?

No guidance is provided on when to use this tool over the many sibling tools with similar purposes. The description lacks any mention of alternative tools or conditions 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?

With no annotations, the description must disclose side effects. It adds one useful negative fact ('No browser is launched') but does not disclose whether the tool makes a network request, how it determines 'can be opened,' or what errors/limitations apply.

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

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

The description is concise and front-loaded with the main action, followed by a relevant behavioral clarification. No fluff or redundant wording is present.

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 ambiguous optional parameters and lack of an output schema, the description leaves important context unexplained: what result is returned, what an 'OK' result means, and how the parameters relate to the check. It is not complete enough for an agent to use confidently.

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 provides no parameter semantics, and the schema's nine optional parameters are confusingly unrelated to the stated purpose. Several descriptions ('Git ref name; discarded after the shape check,' 'City name for a public weather hint') do not clarify how to invoke the URL check.

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

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

The description names a recognizable action and target: 'Check whether a URL can be opened.' However, 'opened' is vague and no mechanism is given, so it does not strongly distinguish from sibling tools like browser-url-ok, fetch-status, 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?

No guidance is given for when to choose this tool over related tools. The only usage hint is the negative behavior 'No browser is launched,' which implies a lightweight check but does not state when it should be preferred.

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 query is discarded after the length check, which is useful side-effect information. However, it does not clarify that the many other schema parameters appear irrelevant or are ignored.

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

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

The description is very concise, using two short sentences that each add value. It states the action and an important side effect without unnecessary elaboration.

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

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

The description does not specify the return value format, the counting unit (e.g., characters vs. bytes), or clarify the role of the other 8 schema parameters. Given the absence of an output schema, this leaves important details ambiguous.

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

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

Although every parameter has a schema description, most descriptions appear copied from unrelated tools and do not align with a simple 'count characters in a query' function. The top-level description does not explicitly state that only the 'query' parameter should be used, creating potential 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's primary function: counting characters in a search query. It is specific enough to distinguish the intended resource, though it does not explicitly contrast with any sibling tool.

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

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

The use case is implied by the description—when a search query's length is needed—but there is no explicit guidance about when to use this tool versus alternatives. No when-not-to-use conditions are stated.

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

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

With no annotations, the description carries full responsibility for explaining side effects and behavior. It only says 'Prompt discarded' and 'Return a three-step thinking template,' leaving unclear whether the tool performs validation, ignores inputs, or has any side effects.

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

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

The description is short, but brevity comes at the expense of clarity. It is front-loaded with the action, yet the rest of the sentence ('Prompt discarded') adds confusion rather than useful 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?

There is no output schema, no annotation, and no explanation of the returned template. With 9 parameters and a vague one-line description, an agent lacks essential context to invoke the tool confidently or interpret its result.

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

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

The schema includes descriptions for all 9 parameters, but they are inconsistent with the tool's stated purpose—e.g., 'Git ref name; discarded after the shape check' and 'JSON text to validate; discarded after the check.' These descriptions do not clarify how the parameters contribute to returning a thinking template.

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' which gives a verb and object, but it does not explain what the template contains, how it relates to the tool name, or how it differs from the many sibling tools. The meaning is too vague to guide selection.

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. The phrase 'Prompt discarded' is cryptic and does not clarify the intended use case or conditions under which the tool should be chosen.

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

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

With no annotations provided, the description carries the full burden. It mentions that the title is discarded, which hints at no persistence, but it does not disclose whether the check performs network access, whether it is read-only, what side effects occur, or what error/response behavior to expect.

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 two short sentences with no filler or redundant wording. It is well within acceptable 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?

There is no output schema, no required parameter indicating the title to check, no explanation of what the return value means, and no mention of failure conditions. The mismatch between the stated purpose and the actual schema makes the tool effectively unusable without external knowledge.

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

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

The input schema contains nine optional string parameters, but none of them represent a Wikipedia title. The descriptions are unrelated to the stated purpose (e.g., 'Git ref name', 'HTTPS URL to normalize or cite'), so the agent cannot determine which parameter to populate for the title check.

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 and object: 'Check whether a Wikipedia title exists.' However, it does not identify which input parameter supplies the title, and the follow-up 'Title discarded after the call' is ambiguous about what title is being referenced.

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

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

No guidance is given about when to use this tool versus any of the many sibling tools such as fetch-status, normalize-url, or search-query-len. The description provides 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.