ISO country MN

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

With no annotations, the description carries the burden, and it does disclose a key non-obvious behavior: 'Task text discarded.' It also states what the tool returns. It does not fully disclose whether remote network calls occur or whether all inputs are ignored, but the main behavioral caveat is surfaced.

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, front-loaded with purpose, and includes only relevant output and behavior information. It could add slightly more invocation clarity without becoming bloated, but as written it is tight and readable.

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 annotations, so the description must compensate. It lists return contents but does not clarify which of the 9 parameters, if any, should be provided, or whether a no-argument call is intended. The schema's 'discarded' notes and zero required parameters partially fill this gap, so the definition is adequate but not complete.

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

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

Schema description coverage is 100%, and each parameter already explains it is a shape check and then discarded. The description adds no real parameter-level meaning beyond 'Task text discarded,' so the baseline score of 3 applies.

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?

States a specific action ('Find') and resource ('public pay-per-call tool gateway (Monid)'), and lists the returned artifacts: CLI setup, how-it-works, skill file, and remote MCP hops. It is clear enough, though 'find' is slightly underspecified and it doesn't explicitly differentiate from sibling tools.

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 intended use is implied: call this when you need Monid gateway setup/instructions. However, there is no explicit when-to-use versus alternatives, no mention of prerequisites, and no guidance about whether to pass any of the 9 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?

With no annotations, the description bears the burden of behavioral disclosure. It usefully discloses that no browser is launched, but it does not explain what 'can be opened' means operationally (e.g., HTTP request, DNS check, side-effect-free) or note that most input parameters are discarded. A clear safety profile 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 extremely concise: two short sentences, no filler. The primary action is front-loaded and the clarifying negative behavior is placed second, making it easy to scan.

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

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

Despite having 9 optional parameters and no output schema, the description gives almost no context about expected return values, error behavior, or how the many inputs relate to the URL check. The schema covers parameter details, but the description leaves too much unspecified for an agent to confidently invoke the tool correctly.

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

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

Schema description coverage is 100%, and each parameter has its own description, including notes about being discarded. The tool description itself adds no parameter-level meaning, so it remains at the baseline of 3 without compensating for gaps or enriching semantics.

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

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

The description states a specific verb and resource: check whether a URL can be opened. The added clarification 'No browser is launched' immediately differentiates it from sibling playwright-url-ok and other browser-related tools.

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 explicit when-to-use guidance and does not mention any alternatives or exclusions. The only contextual hint is 'No browser is launched,' which implies a lightweight check but never tells the agent when to pick this tool over normalize-url, fetch-status, or playwright-url-ok.

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 only says the expression is discarded, hinting at non-persistence, but does not disclose whether the tool returns a numeric result, how invalid expressions are handled, or any side effects. This is insufficient for a tool with no output schema.

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

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

At two short sentences it is very concise and the main verb is front-loaded. The second sentence is ambiguous ('Expression discarded') but it is not padded; however the brevity crosses into 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?

Given nine optional parameters, no output schema, and no annotations, the description is not sufficient for correct invocation. It omits which parameter carries the expression, expected output, and error behavior, leaving most context to be guessed.

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% and each parameter has a descriptive schema comment, meeting the baseline. The description adds no mapping from 'a+b style arithmetic' to any actual property — there is no `expression` parameter — so it fails to help an agent populate the tool call.

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?

States a specific operation ('Evaluate a+b style arithmetic') and names a clear resource (arithmetic expressions), so it is not a tautology. However, it does not explain what 'Expression discarded' means for the return value and does not distinguish from the many shape-check siblings beyond the arithmetic domain.

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 calc-eval versus sibling tools such as search-query-len or validate-json. There are no exclusion conditions, prerequisites, or alternative tool mentions, so an agent must infer usage entirely 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?

With no annotations, the description carries the full burden. It adds one useful behavioral guarantee ('Page content is not stored'), which is valuable for a network-facing tool. However, it does not disclose whether the tool follows redirects, how failures or timeouts are handled, or that it makes a network request beyond what 'HTTP status' implies.

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, front-loaded with the output and followed by a privacy guarantee. No filler or repetition; every sentence contributes.

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

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

The tool has no annotations, no output schema, and nine parameters, yet the description only covers a single URL-centered behavior. An agent gets no guidance about the purpose of the other parameters, expected error behavior, or how this relates to sibling URL/status tools, so the context is not complete enough for reliable selection and invocation.

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

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

The input schema already describes all 9 parameters, so the baseline is 3. The description adds little beyond the schema: it emphasizes that the tool operates on a URL, but does not clarify how the many unrelated-looking parameters (ref, city, feed, json, path) relate to the described behavior.

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

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

The description states a specific verb and resource: it returns host, scheme, and HTTP status for a URL, and adds a meaningful privacy detail. It is clear on its own, but it does not name or distinguish itself from sibling tools such as fetch-status or normalize-url, so it misses the top score.

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 when-to-use guidance is provided. The description does not say whether to choose this instead of fetch-status, browser-url-ok, normalize-url, or web-fetch, nor does it state any conditions or exclusions. The only usage hint is the implicit 'for a URL' in the first sentence.

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 behavioral disclosure burden. It does add a useful privacy statement ('No identifiers are retained'), but it does not describe what happens to the inputs, what output is produced, or whether there are side effects. The schema descriptions mention 'discarded', but the tool description itself is thin.

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

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

The description is a single short sentence plus a privacy note, with no filler and the main action front-loaded. It loses a point because the phrasing is underspecified, but structurally it is concise.

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

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

With nine optional parameters, no output schema, and no annotations, the description is far from complete. It does not explain what the classification result looks like, how the parameters interact, or what an agent should do with the response, leaving too much to inference.

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% and every parameter has its own schema description (e.g., 'Git ref name; discarded after the shape check'). The tool description itself adds no parameter-level meaning, so the baseline score of 3 is appropriate.

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

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

The description states an action ('show') and a vague resource ('this request'), but it never defines what 'classified' means, what classification labels are returned, or how the classification relates to the tool's name. It also does not distinguish this tool from the many similar validation/shape siblings, so the purpose remains ambiguous.

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

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

There is no guidance about when to use this tool versus alternatives like validate-json, normalize-url, domain-shape, or file-path-ok. No conditions, exclusions, or sibling references are provided, leaving the agent to guess which inputs should be routed here.

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 discloses one negative behavioral trait (no WHOIS/ownership enrichment) but says nothing about side effects, return values, or that most accepted inputs are discarded; the 'discarded' notes live in the schema, not the 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 single sentence is tight and front-loaded, with no filler. However, it is under-sized for a tool with nine optional parameters and a large sibling set, so conciseness comes at the cost of necessary context.

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, nine optional parameters, and a large sibling set, the description is not complete enough for reliable invocation. It omits return format, how to select a parameter, and boundaries against related tools such as normalize-url or browser-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?

Schema description coverage is 100%, so the baseline is 3. The description adds a useful 'hostname' semantic for the host parameter, but it fails to explain why ref, city, feed, json, path, zone, and query are accepted or how they relate to splitting a hostname.

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

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

The description gives a specific verb and resource: split a hostname into labels, and clarifies that no WHOIS/ownership enrichment is performed. It does not explicitly distinguish this from sibling shape/check tools, and the nine-field schema muddies the resource, so it stops short of a 5.

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

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

There is no guidance about when to choose this tool over the many sibling check/shape tools, and no explicit when-not-to-use conditions. The 'without WHOIS or ownership data' clause hints at scope but does not route an agent to an alternative.

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. It does disclose a safe HEAD request and that only status is returned, but it omits useful behavior such as redirect handling, timeouts, error responses, and the fact that unrelated schema fields 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 a single front-loaded sentence with no filler. Every word contributes to the core behavior: method, target, and result.

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 many optional parameters, no annotations, no output schema, and multiple URL-checking siblings, one sentence is insufficient. It does not specify the required input field, the shape of the returned status, or how this tool differs from web-fetch and browser-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?

Although schema coverage is 100%, the parameter descriptions are generic and misaligned with this tool: 'url' is described as 'HTTPS URL to normalize or cite' rather than as the target of a HEAD request, and fields like city, feed, json, path, and query are unrelated. The description does not clarify which parameter is the actual 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 clearly states a specific action ('HEAD'), a target ('a public URL'), and an output ('return status only'). This distinguishes it from content-fetching tools like web-fetch, though it does not explicitly name sibling tools.

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 signal is the word 'public'; there is no guidance on when to choose this over web-fetch, browser-url-ok, normalize-url, or playwright-url-ok. No alternative conditions or exclusions are given, so selection is left to inference.

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

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

With no annotations, the description carries the behavioral burden. It does disclose one concrete behavior, 'Path discarded,' but it doesn't say what the parse returns, how invalid URLs are handled, or whether other schema properties are ignored. This is bare-minimum 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?

Two short sentences with no filler. The core purpose is front-loaded, and the behavior note is compact.

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

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

The tool has no output schema and no annotations, yet the description never states the expected result of parsing or the input-output contract beyond discarding path. An agent can make an initial call, but the description alone is incomplete for confident invocation.

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

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

Schema description coverage is 100%, so the schema already documents all parameters. The description adds no parameter details, but it doesn't need to; however, it also doesn't clarify which of the many optional parameters are actually relevant to Figma URL parsing.

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?

States a specific verb 'Parse' with a specific resource, 'a Figma file URL,' making the tool's job unambiguous. Combined with the name, it is readily distinguished from sibling shape-checkers like github-repo-shape or domain-shape.

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

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

The phrase 'Figma file URL' implies the tool should be used when a Figma-specific URL needs parsing, but it does not explicitly mention alternatives or exclusion cases (e.g., generic URLs should go to normalize-url). Usage guidance is implied rather than 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?

The description provides one meaningful behavioral guarantee: 'No disk access', and the phrase 'looks safe' signals a purely syntactic check. However, with no annotations or output schema, it still leaves unspecified what counts as safe, whether a boolean is returned, and how the unrelated schema properties are treated.

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 terse sentences front-load the core action and add a meaningful limitation with no filler. A sentence clarifying which parameter is relevant would make the structure more appropriate for the large schema.

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

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

The tool has no annotations and no output schema, so the description is the only guide. It fails to define safe, specify the return value, or reconcile the unrelated optional parameters, leaving an agent unable to confidently call 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?

Schema description coverage is 100%, so the baseline is 3, and the 'path' property is described as 'File path to check'. The description adds no extra format or syntax detail, and the unrelated optional parameters remain unexplained in relation to 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 name and first sentence identify a specific verb+resource: checking whether a path looks safe, and 'No disk access' clarifies this is a syntactic check rather than a filesystem operation. It falls short of 5 because 'looks safe' is undefined and the nine-parameter input schema muddies what the tool actually operates on.

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 when-to-use or when-not-to-use guidance and no mention of alternatives. An agent must infer from the name and sibling list that this is for file-path validation, with no explicit exclusions such as URL or domain checks.

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 reveals that Open-Meteo is involved; it does not state network dependency, output format, failure behavior, or that several inputs are discarded after the call.

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. It is efficient, though the brevity sacrifices important detail about inputs and 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?

There is no output schema and no annotations, so the description must provide enough context for correct invocation. With nine optional parameters and no mapping from inputs to the returned latitude and longitude, an agent cannot reliably determine which parameter to supply or what the response will look like.

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

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

Schema description coverage is 100%, so the baseline is 3. The tool description adds no parameter-level meaning and does not clarify which of the nine optional parameters is used for the geographic lookup, but the schema already documents each 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 names the output ('Latitude and longitude') and the service ('Open-Meteo'), which distinguishes it from most sibling tools. However, it is a noun phrase rather than a clear statement of what the tool does, and it does not indicate which input identifies the place.

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 alternatives such as weather-hint or timezone. The phrase 'for a place' only vaguely implies geocoding use, but no context, prerequisites, or exclusions 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 explaining behavior. 'Parse owner and repo' suggests a read-only operation, but it does not mention what happens with invalid URLs, whether unrelated parameters are ignored, or what output the agent should 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 a single, front-loaded sentence with no wasted words. It is concise, though it is perhaps too terse to cover the tool's broader behavior and parameter context.

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 annotations, and no output schema, yet the description only covers the core URL parsing function. It does not clarify the role of the other parameters, the return value, or error behavior, so the agent is left with significant ambiguity.

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 in the schema. The tool description adds no parameter-level meaning beyond the schema, which matches the baseline for 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 uses a specific verb and resource: 'Parse owner and repo from a GitHub URL.' It clearly identifies the tool's function and distinguishes it from sibling shape tools such as figma-url-shape, jira-key-shape, and domain-shape by targeting GitHub URLs.

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 the tool should be used when a GitHub URL is available and the agent needs to extract owner and repo. However, it does not explicitly state when not to use it or mention alternatives like normalize-url or other shape-checking tools, leaving some routing guidance implicit.

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

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

With no annotations, the description carries the behavioral disclosure burden. It does add useful behavior: the tool accesses the current front page and discards titles, so output is only a count. However, it does not mention network dependency, rate limits, or the fact that none of the nine optional parameters are required to invoke 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?

Two short sentences with no filler; the action is front-loaded and the qualifications ('current', 'Titles discarded') are placed immediately. Every word earns its place.

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 annotations, so the description should clarify the return value and whether any of the nine parameters matter. It only says 'Count... stories' and 'Titles discarded', leaving the agent to infer the exact return format and the role of the 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?

Schema coverage is 100%, and every parameter already has a description, so the baseline is 3. The tool description adds no per-parameter meaning and does not clarify which of the nine optional fields, if any, affect the count, but the schema itself carries the 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?

Description opens with a specific verb ('Count'), a precise resource ('current Hacker News front-page stories'), and a scoping constraint ('current'). No sibling tool claims this operation, and the additional 'Titles discarded' clarifies that the output is a bare count, not story metadata.

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 establishes a clear use case: obtain the number of current Hacker News front-page stories. It does not explicitly name when-not or alternatives, but the operation is unique among siblings and 'Titles discarded' implicitly tells the agent not to use it when titles are 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?

No annotations are provided, so the description must carry behavioral transparency, but it does not disclose whether the tool is read-only, returns a list, or has side effects. The schema descriptions mention discarded values, but the overall tool 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 description is extremely short, but this is under-specification rather than valuable conciseness. It omits essential information about behavior and parameters, so the single sentence does not earn its place.

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. An agent cannot determine what inputs to provide, what the tool returns, or how this tool fits with the timezone-related sibling tools.

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 description coverage is 100%, the parameters (url, json, path, host, etc.) are unrelated to the stated IANA timezone purpose. The description adds no explanation of how or whether these parameters should be used, creating a semantic mismatch that hurts an agent's ability 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 is a noun phrase, not a clear action statement; it says the tool provides 'Common IANA timezone names for clock calls' but never specifies what the tool does with them (list, validate, suggest, convert?). It largely restates the tool name and does not differentiate it from sibling tools like timezone or utc-time.

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

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

The phrase 'for clock calls' gives only a vague context. There is no guidance on when to use this tool instead of timezone, utc-time, or any other sibling, and no stated exclusions or alternatives.

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

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

The description transparently indicates the operation is a read-only public fetch and that output is deliberately limited to group counts. However, it does not disclose failure behavior (missing robots.txt, 404, malformed content), rate limits, redirects, or whether any input parameters are genuinely used versus discarded, and no annotations cover these aspects.

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

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

The description is one concise sentence with no filler, front-loading both the action and the output restriction. It is tightly written and every word earns its place, though it may be too short for the tool's complexity.

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, no annotations, and no output schema, the description is under-equipped for the tool's complexity. It fails to identify which parameter is the robots.txt target, how the many discarded parameters relate, or what the returned 'group counts' structure looks like, making it difficult for an agent to invoke 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?

Schema description coverage is 100%, so the baseline is 3 even though the main description adds no parameter-specific information. Still, the global description does not map any parameter (e.g., url or host) to the robots.txt fetch, leaving the agent to guess which of the 9 optional parameters 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 uses a specific verb ('Fetch'), a clear resource ('public robots.txt'), and a precise result ('return group counts only'), making the core purpose understandable. However, it lacks sibling differentiation—it does not explain how this differs from web-fetch or fetch-status, and it does not indicate which parameter supplies the site location.

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 such as web-fetch or fetch-status. It names no alternatives, no exclusions, and no selection criteria; the only implied usage is 'when you need robots.txt group counts', which is too weak to guide an agent reliably.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose that the key is discarded, which is useful, but it does not state the return value, whether any external calls are made, or whether only the syntactic shape is validated. For a no-annotation tool, 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 short and front-loaded, and both sentences add some information. However, it is under-specified for a tool with nine parameters and no output schema, so the brevity reflects missing content rather than tight, sufficient coverage.

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

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

With no annotations, no output schema, and nine parameters, the two-sentence description is far from complete. It omits which input carries the Jira key, what the result means, and how this tool relates to the sibling validators. The only complete piece of context is the privacy note that the key is discarded.

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%, giving a baseline of 3, but the description references a 'key' while the schema has no 'key' parameter. The nine schema properties are generic strings (ref, url, city, feed, host, json, path, zone, query) and none are described as Jira issue keys. An agent cannot determine which parameter to populate to check a Jira issue key.

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: 'Check a Jira issue key shape.' This is more than a restatement of the tool name and is reasonably distinguishable from sibling validators like github-repo-shape or domain-shape. However, it does not clarify whether 'shape' means a boolean validity check or a returned shape descriptor, so some ambiguity remains.

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

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

There is no guidance about when to use this tool versus the many sibling validators, no context about appropriate inputs, and no alternatives mentioned. An agent is left to infer usage entirely from the name and the one-line 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 carries the burden; it does disclose that the body is discarded and that the output is an HTTP status. However, it does not explain how the other parameter families behave, what status range is returned, or any side effects such as network calls.

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

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

The description is two short sentences with no filler: the first declares the operation and target, the second states the body-disposal behavior. It is concise and front-loaded, though it achieves conciseness at the cost of completeness.

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 output schema, and no annotations, a two-sentence description is not enough. The description fails to explain how to select among the parameters or what the response looks like beyond a status, making it hard for an agent to use the tool correctly for non-URL inputs.

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

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

The input schema has 100% description coverage, so the baseline is 3. The tool description adds no parameter detail beyond the URL concept; the schema already documents each field, so no additional compensation is needed, but the description also adds no value.

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 — 'HTTP status for a public library docs URL' — but the input schema exposes nine heterogeneous parameters (city, feed, json, path, zone, query) that are not mentioned at all, so the stated purpose is materially incomplete and somewhat misleading about the tool's actual scope.

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

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

There is no guidance on when to choose this tool over siblings like fetch-status, browser-url-ok, web-fetch, normalize-url, validate-json, or weather-hint. The phrase 'public library docs URL' implies one narrow use case but gives no exclusions or alternative 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?

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It does disclose one meaningful trait—'Values discarded'—but it does not explain side effects, return behavior, or the apparent discarding of input parameters mentioned in the schema. This is partial transparency, not complete.

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

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

The description is only two short sentences, front-loaded with the primary action, and each sentence contributes distinct information. There is no redundancy or filler, making it an exemplar of concise tool documentation.

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 too sparse. It does not state which parameter provides the JSON object, what the exact return value looks like, or why the many unrelated-looking parameters exist. An agent would have to infer critical invocation details from names and schema descriptions 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?

Schema coverage is 100%, so the baseline is 3 even without parameter details in the description. The description adds only the generic concept of a 'JSON object' and 'values discarded'; it never maps the JSON input to a specific parameter such as 'json', nor does it clarify the roles of the many other parameters.

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

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

The description states a specific action ('Count') and resource ('keys in a JSON object'), and 'Values discarded' clarifies that value content is irrelevant. It does not explicitly distinguish from sibling tools such as validate-json, and it leaves unclear which input parameter contains the JSON object, so it is not fully disambiguated.

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 there are no exclusions or sibling-tool mentions. The phrase 'Values discarded' implies it is useful when values are unimportant, but this is only implicit and not actionable 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 disclosure burden. It does reveal the key behavioral trait that query strings and fragments are dropped and states the output set. However, it does not mention that only 'url' is honored while the other eight accepted parameters are ignored/discarded, nor does it describe the output format or error 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?

Two short sentences with no filler, and the primary result is stated first. The description is front-loaded and every sentence earns its place. Brevity omits some details, but that is a completeness concern, not a conciseness one.

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 the simple core purpose, the tool exposes nine optional parameters and has no output schema. The description does not clarify that 'url' is the only input that affects the result, does not say how origin/host/path are packaged in the response, and does not cover failure cases. An agent could call it correctly for a simple URL but lacks enough context to handle edge cases or interpret the result 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?

Schema coverage is 100%: each of the nine parameters has a description, including discard behaviors. The description adds no parameter-level meaning beyond 'URL', but the baseline 3 applies because the schema carries the parameter documentation 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?

States a specific action ('Return') on a specific resource ('a URL') and names the output components (origin, host, path). It also adds a distinguishing transformation—query and fragment are dropped—so an agent can tell it from generic URL fetch/check tools. It loses a point because it does not explicitly differentiate itself from sibling URL tools.

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 about when to prefer this over sibling URL tools such as browser-url-ok, domain-shape, or figma-url-shape. There are no explicit when-to-use/when-not-to-use conditions, prerequisites, or alternative tool mentions. Usage must be inferred solely from the action phrase.

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 disclose that no browser is launched, which is useful, but it omits whether a network request is made, what the return looks like, whether there are side effects, or any operational constraints. This is too thin for an agent to predict tool behavior reliably.

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 terse, front-loaded sentences with no filler. The core action and the key behavioral exception are stated clearly and efficiently.

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 annotations, and no output schema, a one-line description is far from complete. It leaves return behavior, parameter selection, and the relationship to sibling tools unexplained, making it insufficient for confident invocation.

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

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

Schema description coverage is 100%, so the parameters are already documented in the schema. However, the description adds no meaning about how the nine optional parameters relate to the stated URL check, and it does not explain why parameters like city, feed, json, path, under zone, or query are accepted.

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

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

Description states a specific action ('Check whether a URL can be opened') and adds the important qualifier that no browser is launched, which distinguishes it from browser-based checks. However, it does not clarify what 'can be opened' means or explicitly differentiate from similar sibling tools like browser-url-ok or fetch-status.

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

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

No explicit guidance is provided on when to use this tool instead of siblings such as browser-url-ok, fetch-status, or normalize-url. The negative statement about not launching a browser hints at a lightweight use case, but the description does not state conditions, alternatives, 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 present, so the description carries the full burden of behavioral disclosure. It adds the useful privacy-related detail that the query is discarded, but it does not state what the tool returns, how the eight other accepted parameters are handled, whether any network or side effects occur, or what happens on failure.

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 no filler. It loses a point because it is so terse relative to a complex 9-parameter, no-annotation schema that it verges on under-specification rather than purposeful brevity.

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

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

Given nine optional parameters, no annotations, no output schema, and many sibling tools, the description is not complete enough for reliable selection and invocation. It does not identify which parameter is relevant, what the response looks like, or how to distinguish this tool from similar sibling tools.

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 all parameters and the baseline is 3. The description itself adds no parameter-level meaning, and it does not clarify why parameters like url, city, feed, and json belong to a tool described as counting search-query characters.

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 operation—counting characters—and a specific resource, a search query, so the core purpose is clear. However, it does not differentiate from similar sibling counting tools, and the 9-parameter schema with unrelated fields makes the intended scope less obvious than it should be.

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

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

The description implies when to use the tool: when you need the character count of a search query. But it provides no explicit guidance about when not to use it, no prerequisites, and no mention of alternative sibling tools such as memory-key-count or hn-front-count.

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

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states a static catalog. It does not reveal whether the tool performs network requests, validations, transforms, or something else, nor any side effects, permissions, or output format.

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

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

The description is only one short sentence, which is technically concise, but it is severely under-specified for a tool with eight parameters and no other context. It fails to front-load any actionable information.

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

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

Given the complexity of the input schema, the absence of annotations and output schema, and the existence of many sibling tools, this description is completely inadequate. An agent cannot know what the tool does, when to call it, or what it returns.

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

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

The input schema provides descriptions for all parameters, so schema coverage is high. However, the tool description adds no meaning about how these parameters relate to HTTP status codes, leaving a significant semantic gap between the catalog description and the actual parameters.

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

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

The description 'Short catalog of common HTTP status codes' is a restatement of the tool name and lacks a verb or resource. It does not specify what action the tool performs or how it relates to the eight diverse input parameters (ref, url, city, feed, host, json, path).

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

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

There is no guidance on when to use this tool versus any of the many siblings like fetch-status, normalize-url, or validate-json. No conditions, exclusions, or alternatives are mentioned.

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

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

With no annotations, the description carries the burden and does disclose one important behavioral trait: the prompt is discarded, implying the tool is stateless and does not use user input. However, it does not explain whether any of the nine input parameters affect the returned template or what the template actually contains.

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

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

The description is two short sentences with no filler. The main action is front-loaded, and the discarded-prompt caveat is a valuable clarification that does not repeat schema 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 simple fixed-template utility, the description is minimally sufficient: an agent can infer that calling it returns a template and that its prompt content is ignored. The lack of any description of the template's structure is a gap, and with no output schema and no annotations, the return value is underspecified, but the tool's low complexity keeps this from being a severe deficiency.

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 parameters are already documented in the input schema. The description adds no parameter-specific meaning beyond the 'prompt discarded' note, which does not map to any listed parameter. The baseline of 3 applies because the schema carries the semantic load.

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

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

The description uses a specific verb ('Return') and resource ('a three-step thinking template'), making the tool's core function clear. It also states that the prompt is discarded, which clarifies what the tool does not do. It does not explicitly compare with sibling tools, but no sibling appears to offer the same fixed-template behavior.

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

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

There is no guidance on when to use this tool instead of another, nor any mention of alternatives or exclusions. 'Prompt discarded' is a behavioral note, not usage guidance, so an agent has little help deciding when to call it.

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

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

With no annotations, the description carries the full behavioral burden, but it only says 'Current time in a named IANA timezone.' It does not disclose output format, invalid-timezone handling, or the fact that the schema's listed parameters are unrelated discarded fields. 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 a single short sentence with no filler and the key idea is front-loaded. It earns its place, though it is arguably too terse given the schema mismatch.

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 simple, but the description omits the only essential calling detail: which parameter carries the IANA timezone. With no output schema and no annotations, the agent lacks both the return contract and the input contract, making correct invocation effectively impossible from the provided text.

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

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

The schema has 100% coverage for its properties, but none of those properties is an IANA timezone name. The description adds no mapping from 'named IANA timezone' to any parameter, so an agent cannot determine how to supply the required input. This is a critical semantic gap beyond the schema's existing descriptions.

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 operation — returning the current time for a named IANA timezone. This clearly distinguishes it from sibling tools like utc-time and iana-zones. However, the description does not reconcile its core concept with the input schema, which contains no timezone parameter.

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

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

The description gives no guidance on when to use this tool versus alternatives such as utc-time or iana-zones. It does not mention exclusions, prerequisites, or how to select among sibling tools. Usage context is only implied by the phrase 'named IANA timezone'.

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 conveys read-only behavior only implicitly through 'current', but does not disclose whether the timestamp is Unix epoch, ISO 8601, or the exact precision. It also fails to clarify that the listed input parameters appear unrelated or are 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 a single, front-loaded sentence with zero filler. For a tool that essentially returns a timestamp, this is appropriately sized.

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

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

With no output schema and no annotations, the description does not provide enough context for an agent to know the expected return format. The unusual input schema with many seemingly irrelevant parameters is not explained in the description, leaving real gaps in 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?

The input schema already documents every parameter with some description, so the schema coverage is high and the baseline is 3. The tool description adds no parameter-specific meaning, and the schema's 'discarded' notes are the only information about how inputs behave.

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

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

The description clearly states that the tool returns the current UTC timestamp, distinguishing it from unrelated siblings. However, it is a noun phrase rather than a verb+resource construction, and it does not explicitly differentiate it from the similar 'timezone' sibling.

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 'timezone' or 'web-fetch'. The description gives no context about expected inputs, output format, or conditions where another tool would be preferable.

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

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

With no annotations provided, the description carries the full burden. It does state that the body is discarded, which is useful for side-effect understanding, but it does not explain the return value (boolean? error?), whether malformed JSON produces an exception, or any limits. The schema's many 'discarded' fields add confusion rather than behavioral clarity.

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 appropriately short: two sentences with no filler. The core action is front-loaded and the discard behavior is stated immediately. The ambiguity of 'body' slightly reduces the value of the conciseness, but the text itself is efficient.

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

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

The tool is simple on its face, but there is no output schema and the description does not describe what a successful check returns or how failures are surfaced. The mismatch between the description and the seven-parameter schema leaves an agent uncertain about which parameter actually receives the JSON body. More context is needed for reliable invocation.

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

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

The input schema has descriptions for all parameters, so schema coverage is high and the baseline is 3. The description itself adds no parameter meaning beyond the schema. The schema's 'json' parameter is clearly described as 'JSON text to validate', but the other parameters appear irrelevant to the stated purpose, and the description does not clarify why they exist.

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: 'Check whether a body is valid JSON.' However, 'body' is ambiguous because the input schema exposes parameters like 'ref', 'url', 'city', and 'path' whose descriptions are unrelated to JSON validation. It does not explicitly map 'body' to any schema field, but the intent is basically understandable.

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 rather than sibling validators like 'domain-shape', 'github-repo-shape', or 'wiki-title-ok'. The description does not state that this is specifically for JSON text or how it differs from other shape-check tools. Usage context must be inferred entirely from the tool name and the one relevant 'json' parameter.

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 disclosure burden. It only discloses the weather behavior, while the schema's repeated 'discarded after the [x] check' parameter descriptions indicate the tool performs broad shape-validation on many input types. An agent cannot anticipate that supplying a URL, JSON, or path yields a validation result rather than weather data.

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 single sentence is efficient and front-loaded with the headline behavior, with no wasted words. However, for a tool with 9 parameters and multiple behavioral modes, this is under-specification rather than true conciseness — the description is not appropriately sized for the tool's complexity.

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

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

With 9 parameters, no annotations, and no output schema, the description carries the full burden and covers only one of the input dimensions. An agent would be drastically under-informed about what inputs are accepted, what is returned for each, what 'discarded' means, and what output format to expect — the description is grossly incomplete.

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 of 3 applies. The description adds only the 'current temperature via Open-Meteo' context for the city parameter and does not clarify how the other eight parameters behave, their precedence, or what happens when multiple are supplied.

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

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

The description states a concrete purpose at face value — retrieving current temperature for a city via Open-Meteo. However, the 9-parameter schema reveals the tool also accepts Git refs, URLs, RSS feeds, hostnames, JSON, file paths, timezones, and search text, so the description critically understates the tool's actual scope. It also doesn't distinguish this from the sibling geo-hint, which plausibly overlaps in the weather/location space.

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 when-to-use or when-not-to-use guidance is provided. This is a notable gap because most of the tool's parameters overlap with sibling tools such as validate-json, file-path-ok, normalize-url, search-query-len, and iana-zones; an agent has no basis to choose weather-hint over those alternatives for non-weather inputs.

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

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

With no annotations, the description carries the full burden, and it does disclose that the body is discarded and the URL must be public. However, it says nothing about redirects, response format, error behavior, or the fact that several schema fields are marked 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 two short sentences, each carrying useful information: what is returned and what is not. There is no filler, repetition, or schema duplication.

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 many sibling tools, this description is too sparse. It does not tell the agent which parameter to populate, whether the other parameters are ignored, or what happens on failure.

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 little beyond the schema except confirming that the URL is the subject of the fetch; it does not clarify the roles of the other eight parameters.

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

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

The description clearly states the deliverable—HTTP status and content type for a public URL—and explicitly says the body is discarded, which distinguishes it from body-returning fetchers. It lacks an explicit verb, but the behavior 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?

The only usage scoping is 'public URL,' implying it is not for authenticated or private targets. There is no guidance on when to use this over siblings like fetch-status, browser-url-ok, or normalize-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?

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'Title discarded after the call,' which hints at statelessness, but it does not explain that the tool likely queries Wikipedia, what it returns, or whether it has side effects. This minimal disclosure 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 a single sentence, so it is concise, but it is under-specified. It lacks any structural detail tying the stated purpose to the schema. The sentence is front-loaded, but its brevity is a defect given the tool's complexity.

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?

This tool has eight parameters, no annotations, and no output schema. The description provides only a purpose statement but no explanation of which parameter to use, what the return value looks like, or any side effects. It is severely incomplete for an agent to invoke correctly.

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

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

The input schema lists eight properties (ref, url, city, feed, host, json, path), none of which is clearly the Wikipedia title. The description says 'Title discarded after the call' but never maps 'title' to a schema property. An agent cannot determine what to pass, so this dimension is fundamentally broken.

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: checks whether a Wikipedia title exists. It goes beyond merely repeating the name and is not vague. However, it does not distinguish itself from sibling tools or mention how the title is supplied, so it stops short of a 5.

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

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

No guidance is given about when to use this tool versus alternatives. There is no indication of prerequisites, exclusions, or preferred scenarios. The description does not mislead, but it provides zero directional context.

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