Milliliters to teaspoons

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

No annotations are provided, so the description carries full burden. It mentions that task text is discarded, which is a behavioral trait, but it does not disclose whether the tool makes external network calls, whether it is read-only, or any side effects. For a tool with no annotations, this is insufficient.

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

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

The description is two sentences with no fluff. It front-loads the purpose and lists the outputs clearly. 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?

With 9 optional parameters and no output schema, the description is incomplete. It does not clarify how parameters like ref, url, or city are used, why they are discarded after checks, or what inputs an agent should provide to get the desired gateway information. This makes correct invocation uncertain.

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

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

The schema descriptions cover 100% of parameters, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides; it does not explain how the optional parameters influence the gateway lookup.

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 finds a public pay-per-call tool gateway (Monid) and lists the returned artifacts (CLI setup, how-it-works, skill file, remote MCP hops). It is specific about the verb and resource, but does not contrast it with any 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?

There is no guidance on when to use this tool versus alternatives. The description only states what the tool does, with no context about selection criteria or conditions that would favor this tool over others like web-fetch or fetch-status.

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. The only behavioral note is 'No browser is launched,' which clarifies it is not a full browser operation. But it does not explain what 'opened' means, whether it makes network requests, what side effects occur, or what happens with the many parameters that are described in the schema as 'discarded.' This is insufficient for a tool with this complexity.

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 terse—a single sentence—which is not appropriate for a tool with 9 parameters and no output schema. It under-specifies the tool's behavior and leaves the agent without sufficient information. While conciseness is valued, here it sacrifices necessary detail.

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 (9 parameters, no annotations, no output schema, many sibling tools), the description is severely incomplete. It does not explain what 'opened' means, what the return value is, which parameters are required, or how this differs from similar tools. An agent cannot confidently invoke this tool correctly based on the description alone.

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

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

The schema descriptions provide 100% coverage and are fairly detailed (e.g., 'Git ref name; discarded after the shape check'). The tool description adds nothing about parameters beyond what the schema already states. Given the high schema coverage, the baseline of 3 is appropriate, but the description does not help map which parameter is the primary URL or how they relate to the tool's purpose.

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

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

The description states a clear action ('Check whether a URL can be opened') and includes a distinguishing note ('No browser is launched'). However, the input schema lists 9 unrelated optional parameters (city, zone, json, path, etc.) that do not clearly map to URL checking, making the tool's actual scope ambiguous. It also does not differentiate from sibling tools like playwright-url-ok or fetch-status, which likely have overlapping purposes.

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

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

There is no guidance on when to use this tool versus the many sibling tools. No context, prerequisites, or alternative recommendations are provided. The description only states what it does, not when it is appropriate.

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. The cryptic statement 'Expression discarded' does not clarify what happens to the expression or the parameters; it only hints that results are not returned, without explaining side effects, output, or error behavior. This is severely inadequate for a tool with 9 parameters.

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

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

The description is extremely short (one sentence), but it is not concise in a helpful way; it is under-specified. It lacks any structured breakdown of the tool's behavior, parameters, or usage, so the brevity harms clarity rather than aiding 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?

Given the tool's complexity (9 optional parameters, no required fields, no output schema) and the lack of annotations, the description is completely inadequate. An agent cannot infer how to invoke the tool correctly, what the parameters mean, what the tool returns, or when to use it. The description covers almost none of the needed context.

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

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

Schema coverage is 100%, so each parameter has a description, but those descriptions (e.g., 'discarded after the shape check', 'discarded after the call') only state that the parameter is discarded, not what it contributes to the operation. The tool description adds no additional meaning about how parameters are used, and it fails to compensate for the fact that the schema descriptions are uninformative about actual functionality.

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 ('Evaluate a+b style arithmetic') but it is misleading because the input schema contains 9 unrelated parameters (ref, url, city, etc.) with no arithmetic-related field. This creates confusion about what the tool actually does, and it does not distinguish it from any of the 28 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?

There is no guidance on when to use this tool vs. alternatives. The description gives no context about intended scenarios, prerequisites, or exclusions, leaving the agent with no basis to choose this over siblings like 'normalize-url' or 'validate-json'.

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

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

With no annotations, the description carries the burden. It does disclose 'Page content is not stored,' which is a useful safety property. However, it does not explain that the tool performs multiple independent checks based on which parameter is supplied, nor does it disclose that most parameters are 'discarded after the check' as the schema indicates. The description adds some behavioral context but misses the multi-purpose nature of the tool.

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 fluff. It front-loads the primary function and adds a relevant safety note. Every word earns its place. This is an exemplary model of conciseness.

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

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

The tool has nine parameters, none required, and no output schema. The description covers only the URL behavior, leaving the purpose and interaction of the other eight parameters unexplained. An agent cannot infer when to use this tool for city, feed, json, etc., or what the return format will be. The description is insufficient for a multi-parameter tool of this complexity.

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

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

Schema description coverage is 100%, so every parameter already has a description. The tool description adds meaning to the 'url' parameter by specifying the output (host, scheme, HTTP status), but it provides no extra semantic value for the other eight parameters. Since the schema already documents them, the baseline of 3 is appropriate, with a slight bonus for the URL clarification but not enough to raise the score.

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: 'Return host, scheme, and HTTP status for a URL.' This clearly identifies the core function and distinguishes it from generic tools. However, the tool's schema includes eight additional parameters (city, feed, json, etc.) that are not mentioned in the description, so the stated purpose is incomplete regarding the full scope of the 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?

No guidance is given on when to use this tool versus alternatives like fetch-status, normalize-url, or web-fetch. The description does not mention any exclusions, prerequisites, or conditions that would help an agent decide between this and sibling tools. The only implicit hint is the main purpose, but no explicit routing is provided.

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

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

With no annotations, the description must carry the full behavioral burden. It only offers a privacy guarantee ('No identifiers are retained') but does not disclose whether the tool performs any external calls, mutates state, or what side effects exist. The per-parameter notes about discarding data are in the schema, not the description, and are not summarized.

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 (two sentences) and could be concise, but it is under-specified. It lacks critical information about purpose and usage, so its brevity is a deficit rather than a strength. The front-loaded 'Show how this request is classified' is not informative.

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

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

This is a 9-parameter tool with no output schema, no annotations, and a vague one-line description. The agent is left without any idea of what the tool returns, when to invoke it, or how to interpret its results. The description is far from sufficient for correct 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 fully documents each of the 9 optional parameters. The tool description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 applies. It does not explain how the parameters relate to the classification.

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

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

The description states a purpose but it is vague: 'Show how this request is classified' does not specify what classification means, what resource is acted on, or what output is produced. It does not differentiate from sibling shape-checking tools like domain-shape or validate-json, which each have clear, specific purposes.

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

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

No guidance is given on when to use this tool versus the many siblings. There is no mention of conditions, alternatives, or exclusions. An agent would have no idea when to prefer 'compatibility' over a specific shape-checker like github-repo-shape.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does mention 'without WHOIS or ownership data,' which is a useful constraint, but it fails to explain that the tool also processes the other 8 parameters and that most are 'discarded after the check' (as the schema notes). This omission is misleading, as an agent might assume only 'host' matters.

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 fluff, which is appropriately concise. However, its brevity comes at the cost of completeness—it omits nearly the entire parameter space. Still, for what it does say, it is well-structured and front-loaded with the core action.

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

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

This is a tool with 9 parameters, no output schema, and no annotations. The description only covers hostname splitting, ignoring the other eight parameters entirely. An agent cannot determine what inputs to provide, what the tool does with them, or what output to expect. This is critically incomplete for the tool's complexity.

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

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

Schema coverage is 100%, so the baseline is 3. The description adds no parameter meaning beyond the schema; it doesn't even reference the other parameters or clarify how they relate to the 'hostname splitting' purpose. It neither reinforces nor extends the schema descriptions, leaving the agent to rely solely on the schema.

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

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

The description states a specific action ('split a hostname into labels') and even differentiates from WHOIS/ownership data, which separates it from some sibling shape tools. However, the tool's schema accepts 9 heterogeneous parameters (url, city, json, path, zone, etc.) that are not mentioned at all, so the description does not accurately convey the tool's full purpose. It reads like a narrow hostname-specific tool when it clearly handles many input types.

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 siblings like github-repo-shape or jira-key-shape. The description offers no context about typical use cases, prerequisites, or conditions that would select this tool over alternatives. An agent would have to infer usage from the name and description, which is insufficient.

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 discloses that only a HEAD request is made and only status is returned, which is useful. However, it does not mention that many parameters are 'discarded' per the schema, nor does it describe side effects, rate limits, or error behavior. The gap between the description's narrow URL focus and the schema's broad parameter set is unexplained.

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, front-loaded with the core action and output. It is concise and waste-free, though its brevity contributes to the under-specification noted in other dimensions.

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

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

The tool has 9 optional parameters, no output schema, and no annotations. The description only covers the URL scenario, leaving the agent without guidance on how to use the other parameters or when they apply. The complexity of the schema is not matched by the description, so an agent cannot confidently determine the correct invocation for non-URL tasks.

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

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

Schema coverage is 100%, so each parameter is individually documented. The description adds no extra meaning beyond the schema; it only reinforces the URL parameter's purpose. Since the schema already handles parameter semantics, a baseline of 3 is appropriate, though the description does not help disambiguate which parameters are relevant for the stated HEAD operation.

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

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

The description states a clear verb and resource ('HEAD a public URL and return status only'), but the schema exposes 9 parameters of which only 'url' matches that stated purpose. It does not explain why the other parameters (city, feed, json, path, zone, query, etc.) exist, creating ambiguity about the tool's actual scope. This undermines the clarity of its purpose.

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

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

No guidance is given on when to use this tool versus sibling tools like browser-url-ok, playwright-url-ok, web-fetch, or domain-shape. The description does not mention alternatives, exclusions, or selection criteria, leaving the agent to guess.

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

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

With no annotations, the description carries the full burden of disclosing behavior, but it only says 'Path discarded.' It does not mention that other parameters are also discarded, what the function returns, or whether it performs any network access. The minimal disclosure is inadequate for a tool with 9 parameters.

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

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

The description is one sentence and front-loaded, but it is under-specified rather than concise. It omits critical information needed to use the tool correctly, so the brevity is a drawback, not a strength.

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

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

For a tool with 9 optional parameters, no output schema, and no annotations, this description is woefully incomplete. It does not explain the return format, the purpose of each parameter, or how the tool handles invalid inputs. An agent cannot determine correct invocation from this description alone.

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

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

The schema provides 100% coverage, so the baseline is 3, but the description adds no value beyond that. Worse, the description's mention of 'Path discarded' conflicts with the schema's description of the path parameter ('File path to check; no disk access'), creating confusion. The description fails to explain how the various parameters relate to the stated Figma URL 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 'Parse a Figma file URL' with a clear verb and resource, but it is vague about what parsing entails or what output is produced. It does not distinguish this tool from siblings like normalize-url or browser-url-ok, and the presence of many unrelated parameters (city, feed, json) makes the actual scope 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?

No guidance is provided on when to use this tool versus alternatives. It does not mention any exclusions or conditions, leaving the agent to infer usage from the name alone. The description is silent on the role of the non-URL 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 mentions 'No disk access,' which is a useful behavioral note, but it does not disclose how the other parameters are handled, what the tool returns, or any side effects. Since annotations are absent, the description carries the full burden, and it fails to explain the behavior for most of the schema fields.

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 efficient conciseness. For a tool with 9 parameters and no output schema, a one-sentence description is inadequate and fails to front-load essential information. The brevity is not earned because it leaves critical details out.

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

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

Given the tool has 9 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the tool does with the majority of the parameters, what it returns, or how the parameters relate to the stated path-safety purpose. An agent would have no way to correctly invoke this tool for any of the non-path 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?

The schema has 100% description coverage, so each parameter is documented in the schema itself. The tool description adds no additional meaning about the parameters, so the baseline of 3 applies. It neither clarifies the relationship between the parameters nor provides any usage hints beyond the schema.

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

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

The description states 'Check whether a path looks safe' which is a specific verb and resource, but the input schema contains 9 unrelated parameters (ref, url, city, feed, host, json, zone, query, etc.), making the actual purpose ambiguous. It does not distinguish from sibling tools like browser-url-ok or validate-json, and the name suggests a narrow scope that the schema contradicts.

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 vs alternatives. The description provides no context about when it is appropriate, what it does with the non-path parameters, or how it relates to sibling tools. This is a complete absence of 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, the description carries the full burden, but it only states the output without disclosing that most parameters are discarded after checks, that it is a hint (not authoritative), or how it interacts with Open-Meteo. The parameter descriptions hint at varied behaviors, but the main description omits them.

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 waste, but it is too brief to be functional. It lacks any structure or elaboration, making it under-specified rather than 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?

For a tool with 9 optional parameters, no output schema, and no annotations, this description is severely inadequate. It does not explain return format, error handling, or how to choose inputs, leaving the agent with virtually no guidance.

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 themselves are inconsistent with the tool's stated purpose (e.g., 'city' mentions weather hints, 'ref' is a git ref). The main description adds no clarification about which parameter is the primary input or how they combine, so an agent cannot determine correct usage.

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 ('Latitude and longitude for a place via Open-Meteo') but the tool's 9 unrelated parameters (ref, url, feed, host, json, path, zone, query) conflict with this narrow purpose, making the actual function ambiguous. It does not distinguish from siblings like weather-hint or timezone.

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

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

No guidance is given on when to use this tool versus alternatives like weather-hint, timezone, or iana-zones. There is no mention of conditions, prerequisites, or which parameter to supply for a given use case.

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 full responsibility. It states the core action but discloses no behavioral traits: no mention of error handling on invalid URLs, no mention of return format, no mention that the other parameters are ignored. The description is too terse to reveal how the tool behaves beyond its primary intent.

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?

A single, precise sentence with no redundancy. It is front-loaded with the action and resource, and every word earns its place. This is an exemplar of conciseness.

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

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

For a tool with 9 parameters, no output schema, and no annotations, the description is incomplete. It does not explain the return value, how the URL is parsed, or why the other parameters exist. An agent cannot fully anticipate behavior or errors, especially given the unusual mix of 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?

The schema describes all 9 parameters, and the description clarifies the purpose of the 'url' parameter by linking it to owner/repo extraction. However, the description ignores the 8 other parameters, which the schema marks as discarded or irrelevant. This leaves ambiguity about whether they are used, though the schema coverage is 100% and the description adds value for the primary parameter.

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

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

The description states a specific verb and resource: 'Parse owner and repo from a GitHub URL.' This clearly differentiates it from sibling shape tools like domain-shape or jira-key-shape by naming the exact input and output. It is unambiguous and 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that it is for extracting owner/repo from GitHub URLs only, nor does it contrast with similar tools like normalize-url or browser-url-ok. An agent would have to infer usage from the name alone.

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

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

No annotations are provided, so the description must carry the full burden. It only notes that titles are discarded, but does not disclose whether the operation is read-only, what side effects occur, or what the return value is. The behavior remains largely opaque.

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

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

The description is extremely short (one sentence), but this is under-specification rather than concise adequacy. Critical information about parameter usage and output is omitted, so the brevity is not beneficial.

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

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

With nine parameters, no output schema, and no annotations, the description fails to explain how inputs are used, what the tool returns, or how the counting is performed. The phrase 'Titles discarded' adds little clarity. The definition is severely incomplete for an agent to call it correctly.

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

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

While schema coverage is 100% (each parameter has a description), the tool description does not explain how any of the nine parameters relate to counting HN stories. The schema descriptions are generic and the tool description adds no mapping, leaving the parameters' purpose in this context unclear.

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

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

The description states a specific action ('Count current Hacker News front-page stories') but the input schema contains nine generic parameters (ref, url, city, feed, host, json, path, zone, query) with no obvious connection to counting HN stories. This mismatch 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?

The description provides no guidance on when to use this tool versus the many sibling tools, nor does it mention any prerequisites or exclusions. A single declarative sentence offers no contextual routing.

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

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description discloses nothing about what happens when called—whether it returns a list, validates input, or is a constant. There is zero transparency about side effects, return values, or constraints.

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 effective conciseness. A single vague sentence does not earn a high score because it omits essential information. The structure lacks any front-loading of key details.

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 nine parameters, no annotations, and no output schema, the description is grossly inadequate. It fails to explain the purpose, behavior, or how the parameters relate to IANA zones. An agent cannot reliably decide to call this tool or understand its output.

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

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

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter-specific meaning beyond the schema's own descriptions, which already document all nine parameters. Since the schema covers everything, the description does not need to compensate, but it also adds nothing extra.

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 verb+resource. It states 'Common IANA timezone names for clock calls' but never specifies what the tool actually does—whether it validates, lists, or converts timezone names. It lacks a clear action or operation, and it doesn't differentiate itself from siblings like 'timezone' or 'utc-time'.

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

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

There is no guidance on when to use this tool versus alternatives. It only mentions 'clock calls' without defining the context or exclusions. No sibling tool is named, and no conditions 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 provided, so the description carries the full burden of behavioral disclosure. It states the action and output type but does not mention error handling, what happens if the URL is invalid, rate limits, or any side effects. This is minimal for a network-fetching tool.

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 fluff, front-loading the core action and output. It is concise and easy to parse, though it sacrifices necessary detail for brevity.

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

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

With 9 optional parameters and no output schema, the description is insufficient. It doesn't explain which parameters are relevant, how the input should be structured, or what the 'group counts' format looks like. An agent would struggle to invoke this tool correctly without additional information.

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

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

Although schema coverage is 100%, the tool description adds no parameter-specific meaning. The schema descriptions are generic (e.g., 'HTTPS URL to normalize or cite') and do not indicate which parameter is used for the robots.txt fetch. The description fails to clarify the mapping between parameters and the tool's purpose, leaving ambiguity for the 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 clearly states the action (fetch) and resource (robots.txt), and specifies the output is 'group counts only'. This is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like web-fetch or fetch-status, so it loses a point for lacking explicit sibling distinction.

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

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

There is no guidance on when to use this tool versus alternatives. No mention of use cases, prerequisites, or exclusions. The description simply states what it does without any context for selection.

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

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

The only behavioral disclosure is 'Key discarded', which is cryptic and does not explain what happens to the other inputs, whether the tool returns a boolean or status, or any side effects. With no annotations provided, the description carries the full burden and fails to provide meaningful transparency.

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

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

The description is a single sentence with no wasted words, which is concise. However, it is too brief to be structurally useful; key information about which parameter to use is missing. Concise but under-specified.

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

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

With 9 parameters, no output schema, and no annotations, the description is severely incomplete. An agent cannot determine which parameter to pass, what the expected Jira key format is, or what the tool returns. The description provides almost no context for correct 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 coverage is 100%, so each parameter is already documented in the schema. The description adds no additional meaning about which parameter is the Jira key or how parameters relate to the check. It merely repeats the discard note already implied by the schema descriptions, providing no added value beyond the baseline.

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

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

The description states 'Check a Jira issue key shape' which is a specific verb and resource, but it does not specify which of the nine input parameters holds the key. This ambiguity makes it unclear how to invoke the tool correctly. It also does not distinguish itself from sibling shape-checking tools like domain-shape or github-repo-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?

There is no guidance on when to use this tool versus alternatives, no mention of required inputs, and no context about typical use cases. The description is a single sentence with zero 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?

The description notes 'Body discarded,' which is a behavioral detail, but with no annotations it fails to disclose network behavior, error handling, rate limits, or how the various parameters affect the operation, leaving significant behavioral gaps.

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

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

The description is a single sentence, which is concise, but it is under-specified for a tool with 9 parameters; it front-loads the purpose but omits crucial context, making it not appropriately sized for the 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 fails to explain the purpose of the many parameters, the output format, or how the tool handles different inputs, making it nearly impossible for an agent to use correctly.

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

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

Schema coverage is 100% with each parameter described, so the description does not need to repeat them; however, it adds no new meaning about how parameters interact or which are relevant to the stated purpose, so it remains at the baseline.

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

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

The description states a specific action (HTTP status) and resource (public library docs URL), but the input schema includes 9 unrelated parameters (city, feed, host, json, path, zone, query) with no explanation, creating ambiguity about the actual scope and making the purpose unclear for an agent.

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 sibling tools like browser-url-ok or fetch-status; there is no mention of alternative selection criteria, leaving the agent without a basis to choose this tool.

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

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

The description discloses that values are discarded, which is a behavioral detail, but it omits other important behaviors such as whether it validates JSON, performs network access, or has side effects. With no annotations, the description carries the full burden and falls short.

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

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

The description is extremely concise but under-specified. While it is front-loaded with the core action, it lacks necessary detail for an agent to use it correctly, making it inappropriately 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?

Given the tool's complexity (9 parameters, no output schema, no annotations), the description is grossly incomplete. It doesn't explain the return value, edge cases, or how to interpret results, leaving the agent with insufficient information.

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

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

The schema already describes all 9 parameters with 100% coverage, so the description doesn't need to repeat them. However, the description adds no extra meaning about how these parameters relate to the counting operation, such as which parameter is the JSON object or how others 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?

The description states a clear verb and resource ('Count keys in a JSON object'), but it is ambiguous how this applies to the 9 parameters in the schema, many of which are not JSON objects (e.g., ref, url, city). It does not differentiate from siblings like validate-json 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?

No guidance on when to use this tool versus alternatives. There is no mention of conditions, exclusions, or context that would help an agent choose it over similar tools.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The claim of unit conversion is contradicted by the schema, which expects generic parameters like URLs, city names, and JSON text—none of which relate to the stated purpose. This is a serious behavioral inconsistency that would mislead an agent.

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 conciseness. It lacks any structural elements, such as front-loaded key information, and offers no substantive content that would help an agent understand the tool's function or invocation.

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

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

For a tool with 9 parameters, no required fields, and no output schema, this description is completely inadequate. An agent cannot determine which parameters are relevant, what the tool does with them, or what the expected output or side effects are. The description fails to provide any actionable information for correct invocation.

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

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

Although the schema has 100% coverage with parameter descriptions, the tool description adds no meaning that connects these parameters to the claimed milliliters-to-teaspoons conversion. The parameters appear entirely unrelated to the purpose, so the description fails to explain how they should be used or what each represents in the context of the tool.

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

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

The description 'Milliliters to teaspoons' suggests a unit conversion tool, but the schema parameters (ref, url, city, feed, host, json, path, zone, query) have no relation to milliliters or teaspoons. This mismatch makes the purpose misleading and unclear; it fails to state a clear verb-resource action and does not distinguish from any 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?

There is no guidance on when to use this tool versus alternatives. The description provides no context about intended use cases, prerequisites, or conditions that would select this tool over others like calc-eval or 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?

With no annotations, the description must carry the full behavioral burden. It discloses that query and fragment are dropped, which is useful, but it completely ignores the other eight parameters defined in the schema, leaving their behavior undisclosed. The description implies the tool only processes URLs, yet the schema suggests it accepts many other inputs, creating ambiguity about what happens when those are provided.

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

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

The description is a single, focused sentence with no wasted words. It front-loads the core purpose and includes a key behavioral detail. It is appropriately concise for the stated functionality.

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

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

The tool has 9 parameters but the description only addresses one. There is no output schema, so the agent has no idea what the return format is beyond the vague 'origin, host, and path.' The mismatch between the narrow description and the broad schema makes the definition incomplete for an agent trying to decide whether to use it and how to interpret results.

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 described. The tool description adds nothing about parameters beyond mentioning 'URL' and the fact that query/fragment are dropped, which is already implied by the schema. This meets the baseline of 3 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 clearly states a specific action: 'Return origin, host, and path for a URL.' It is unambiguous about the primary function. However, it does not differentiate from sibling tools like browser-url-ok or figma-url-shape, which might also deal with URLs, so it misses the opportunity to disambiguate.

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

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

The description provides no guidance on when to use this tool versus alternatives. It only states what it does and that query/fragment are dropped, which is behavioral rather than contextual. There is no mention of exclusions, prerequisites, or comparisons to other tools.

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

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

With no annotations, the description carries the full behavioral burden. It discloses that no browser is launched, but it does not explain how the URL is checked (e.g., HTTP request, DNS lookup), what the return value is, or how failures are handled. The tool also accepts 9 unrelated parameters, yet the description does not clarify why or what happens to them, leaving major behavioral gaps.

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

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

The description is a single, tightly written sentence that states the core purpose and a key constraint. It is efficient and front-loaded, with no redundant wording. However, the extreme brevity is not justified given the tool's complexity; it sacrifices necessary detail.

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 9 parameters, no annotations, no output schema, and many sibling tools, yet the description is just one sentence. It fails to explain what the tool does with the non-URL parameters, what output it produces, when it should be used, or how it differs from alternatives. For a tool with this complexity, the description is severely 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?

Although schema description coverage is 100%, the descriptions are cryptic (e.g., 'discarded after the shape check') and the tool description adds no clarification about how parameters relate to the stated purpose of checking a URL. Many parameters (ref, city, feed, json, path, zone, query) appear irrelevant to a URL check, and the description does not explain their role, leaving the agent confused about which parameters are actually needed.

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

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

The description clearly states the tool checks whether a URL can be opened, with the explicit addition that no browser is launched. This gives a specific verb and resource. However, it does not differentiate it from siblings like 'browser-url-ok' or 'fetch-status' beyond the no-browser note, which is an implicit distinction rather than an explicit one.

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

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

The description offers no guidance on when to use this tool versus alternatives. It does not mention any sibling tools, prerequisites, or scenarios where this tool is preferred. An agent has no basis for selecting it over similar tools.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Query discarded,' which is vague and does not clarify side effects, network access, return values, or which parameters are actually used. The schema hints at side-effect-free checks (e.g., 'no disk access'), but the description itself adds no behavioral context.

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 (two sentences), but it is under-specified rather than concise. It omits essential information about the tool's operation and the role of its parameters. The structure does not front-load useful context because the single statement is ambiguous.

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

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

With 9 optional parameters, no annotations, no output schema, and a complex set of sibling tools, the description is grossly inadequate. It does not explain what the tool returns, whether it performs validation, which parameters are relevant, or what 'discarded' means operationally. An agent cannot reliably select or invoke this tool based on the current description.

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

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

Although schema description coverage is 100%, the tool description does not map the parameters to its purpose. It only references a 'search query' without specifying which parameter that is (presumably 'query'), and it ignores the other 8 parameters. The description fails to explain how the parameters are used or why they exist, leaving the agent to guess the tool's actual 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 verb and resource ('Count characters in a search query'), but it is misleading because the schema lists 9 optional parameters, not just a search query. It does not explain what happens with the other parameters (ref, url, city, feed, host, json, path, zone) or how they relate to the stated purpose. The phrase 'Query discarded' is contradictory and unclear.

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

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

There is no guidance on when to use this tool versus the 28 sibling tools, many of which are shape-validators (e.g., domain-shape, github-repo-shape). The description does not mention any 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails entirely: it doesn't state whether the tool makes network requests, performs validation, or returns a status code. The parameter descriptions in the schema mention 'discarded after the shape check' and 'no disk access', but these are in the schema, not the description. The description offers no insight into side effects, input handling, or return 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 in length (one sentence), but it is under-specified rather than appropriately concise. For a tool with 9 parameters, a one-sentence description that omits all functional detail is not acceptable conciseness; it's a deficiency. The structure is fine, but the content is insufficient.

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 (9 optional parameters, no output schema, no annotations), the description is grossly incomplete. It doesn't explain what the tool does with the inputs, what it returns, or how it relates to the catalog. An agent cannot call this tool correctly without additional knowledge. The description fails to provide any operational context.

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

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

Schema description coverage is 100%, so each parameter has a description. The baseline for high coverage is 3. The description adds no additional meaning beyond the schema; it doesn't mention how parameters influence the result. The schema descriptions themselves provide some semantics (e.g., 'discarded after the shape check'), but these are part of the schema, not the tool description. The description contributes nothing to parameter understanding.

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 noun phrase that states what the tool is, not what it does. It lacks a verb (e.g., 'returns', 'lists', 'provides') and gives no indication of how the 9 input parameters relate to the catalog. It does not distinguish itself from siblings like fetch-status or browser-url-ok, which are clearly about checking status. The name 'status-catalog' suggests a reference, but the parameters imply some checking behavior, creating 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?

There is no guidance on when to use this tool versus alternatives. The description never mentions any sibling tool, use case, or exclusion criteria. An agent cannot determine whether this should be used instead of fetch-status, domain-shape, or any other status-related tool. The description is a single sentence with no context.

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

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

With no annotations, the description must carry full behavioral disclosure. It states that the prompt is discarded, but does not explain that all 9 parameters are validated and then discarded, nor that the output is a fixed template independent of inputs. The schema descriptions hint at this ('discarded after the shape check'), but the tool description itself is vague and potentially misleading about what happens with the inputs.

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. The key point (return a template) is front-loaded, and there is no unnecessary filler. However, the brevity borders on under-specification, which slightly detracts from its usefulness.

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

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

For a tool with 9 parameters, no output schema, and no annotations, the description is inadequate. It does not describe the content of the three-step template, nor does it explain the role of the parameters (even if they are discarded). An agent would not know what the template looks like or what to expect as a result, making the tool difficult to use correctly.

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

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

The schema description coverage is 100%, so each parameter is already documented. The description adds no meaning beyond the schema; it only mentions the prompt being discarded, which does not clarify parameter semantics. Given high schema coverage, the baseline of 3 is appropriate, but the description does not enhance understanding of how parameters influence 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 clearly states the tool returns a three-step thinking template, which is a specific verb and resource. However, it does not differentiate it from the many sibling tools, as there is no mention of when this template is appropriate or how it differs from other tools like citation or calc-eval.

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. The phrase 'Prompt discarded' is confusing and does not clarify the tool's purpose or usage context. There is no mention of exclusions or conditions, making it impossible for an agent to decide 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 must disclose behavior. It only states the purpose and does not mention that the other 8 parameters are ignored, whether the operation is read-only, or what the return format looks like. It also doesn't clarify that it may rely on local timezone data or network access. This is a significant gap for a tool with 9 parameters.

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

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

A single, clear sentence with no fluff. It is appropriately brief for a simple purpose, though it could have added a note about ignored parameters without bloat.

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, so the description should explain what the return value is. It only says 'current time' but not the format or structure. Additionally, it does not address the irrelevant parameters or any error conditions. For a tool with 9 parameters and no annotations, this is under-specified.

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

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

The schema descriptions for all parameters are detailed and indicate that most are discarded. The tool description adds nothing beyond the schema, but since schema coverage is 100%, the baseline is 3. The description could have explicitly stated that only 'zone' is used, but the schema already conveys this, so no extra value is provided.

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

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

The description states a specific action: get current time in a named IANA timezone. It clearly indicates the resource and scope, distinguishing it from utc-time (which presumably returns UTC) and iana-zones (which likely lists zones). However, it does not explicitly name these siblings, so differentiation is implicit.

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

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

No guidance on when to use this tool versus alternatives like utc-time or iana-zones. The description does not mention any prerequisites, fallback logic, or exclusions. An agent would have to infer from the name alone.

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

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

No annotations are provided, so the description must fully disclose behavior. It only says 'Current UTC timestamp,' but the input schema reveals 9 parameters that are mostly discarded after validation. The description does not mention that parameters are ignored or that the tool performs validation checks, leaving significant behavioral aspects undisclosed. This is a substantial transparency gap for a tool with such an unusual parameter set.

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

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

The description is extremely concise, consisting of a single sentence with no wasted words. It is front-loaded and immediately comprehensible. However, the extreme brevity omits crucial information, so while it scores high on conciseness, the lack of structure (no headings or additional details) limits its effectiveness.

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

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

With 9 optional parameters and no output schema, the description is inadequate for an agent to understand how to call the tool correctly. It does not explain whether parameters are necessary, what the return format is, or why the tool accepts a variety of unrelated inputs. The complexity of the schema is not addressed at all, making the description incomplete for practical usage.

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

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

Schema description coverage is 100%, so each parameter has a description that explains its type and purpose (e.g., 'Git ref name; discarded after the shape check'). However, the main tool description does not tie these parameters together or explain their relevance to returning a UTC timestamp. The parameter descriptions are self-contained but leave an agent wondering why such a simple tool accepts these inputs. Baseline 3 is appropriate since the schema does the heavy lifting, but the description adds no additional meaning.

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

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

The description states a clear verb and resource: 'Current UTC timestamp.' It specifies exactly what the tool returns and distinguishes it from siblings like timezone or iana-zones, though it does not explicitly mention those alternatives. The purpose is not a tautology and is immediately understandable, though it omits any reference to the tool's parameter handling.

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

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention any specific use cases, prerequisites, or exclusions. With 28 sibling tools including timezone and iana-zones, an agent receives no direction on selection. The single sentence gives no context about the tool's role or limitations.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'The body is discarded,' which is ambiguous because 'body' isn't a schema parameter. It does not mention whether the tool returns a boolean, throws an error, or how it treats the other eight parameters. This is insufficient for an agent to predict tool behavior.

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

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

The description is only two sentences, which is concise but severely under-specified. It lacks essential information such as which parameter to use and the return format. The brevity is not an asset because it omits critical operational details; it feels truncated rather than efficiently front-loaded.

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

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

For a tool with nine parameters and no output schema, the description is drastically incomplete. It doesn't explain the purpose of the other parameters, what the tool returns, or how it should be invoked. An agent has no way to construct a correct call based on this description alone, making it inadequate for the tool's complexity.

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

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

Despite 100% schema description coverage, the description adds no parameter meaning and actually introduces confusion by referring to a nonexistent 'body'. It does not mention that 'json' is the parameter to validate, nor clarify whether the other parameters are relevant or ignored. This actively misleads rather than aiding parameter selection.

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 checks JSON validity, but uses 'body' which is not a parameter name in the schema. It doesn't specify which parameter holds the JSON text, and it doesn't differentiate from sibling validation tools like 'domain-shape' or 'file-path-ok'. The verb 'Check' and resource 'JSON' are present, but the ambiguity about the input undermines clarity.

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

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

There is no guidance on when to use this tool versus alternatives. It doesn't say 'use this when you need to validate a JSON string' or mention any constraints like requiring a specific parameter. The absence of context leaves an agent uncertain whether this is the right tool for a given JSON validation task.

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

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not state whether the operation is read-only, what it returns (temperature units, format), whether there are side effects, or how it handles the many parameters that are not city-related. The description is silent on behavior beyond the basic claim.

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

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

The description is a single sentence, which is concise and front-loaded with the core purpose. However, it is under-specified; it does not explain the role of the many parameters or the output. It is concise but not informative, so it does not earn its place beyond a basic statement.

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

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

The tool has 9 parameters, none required, and no output schema. The description covers only the city-temperature use case and ignores the other parameters, which are all described in the schema as 'discarded' or 'checked'. It does not explain the tool's overall behavior or how the parameters interact, leaving the agent guessing. This is a significant gap for a multi-parameter 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?

Schema coverage is 100%, but the parameter descriptions are generic and unrelated to the weather purpose (e.g., 'ref' is a Git ref, 'url' is a URL). The description adds no meaning to parameters; it only implies 'city' is relevant. The schema's descriptions do not clarify how to use them for this tool, so the description fails to compensate.

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 ('Current temperature'), a resource ('temperature for a city'), and a source ('via Open-Meteo'). It is clear about the primary function, though it does not differentiate from siblings like 'geo-hint' or 'lib-docs-hint'. The narrow scope conflicts with the broad schema, creating ambiguity about the tool's actual 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?

The description offers no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or scenarios where a different sibling (e.g., 'geo-hint') would be more appropriate. The single sentence leaves the agent to infer usage from the schema, which is insufficient.

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

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

With no annotations, the description carries the burden of behavioral disclosure. It states 'Body discarded', which tells the agent that content is not returned, and implies the tool is read-only and safe for public URLs. However, it omits details on error behavior, rate limits, or any side effects, leaving significant gaps.

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

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

The description is extremely concise, using a single sentence with two clauses. It is front-loaded with the core purpose and quickly states the body-discarding behavior. While it is not overly verbose, it is so short that it borders on under-specification rather than elegant conciseness.

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

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

Given the tool has 9 parameters, all optional, and no output schema, the description is severely incomplete. It claims to return HTTP status and content type for a URL, but the parameters include ref, city, feed, host, json, path, zone, and query, which are not explained in the description. An agent cannot determine how these parameters influence the tool's behavior or whether they are used at all. The description fails to cover the tool's full scope.

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, with each of the 9 parameters having its own description. The tool description adds no additional meaning beyond what the schema already provides, so the baseline of 3 is appropriate. It does not clarify how the many seemingly unrelated parameters (city, zone, query, etc.) relate to the stated purpose of HTTP status/content type.

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 it fetches HTTP status and content type for a public URL, with body discarded. This is a specific verb and resource, but it doesn't differentiate from siblings like fetch-status or browser-url-ok, which may overlap. Without comparison, the purpose is clear but not unique among the sibling set.

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

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

No guidance is provided on when to use this tool versus alternatives like fetch-status, normalize-url, or browser-url-ok. There is no mention of conditions or exclusions, leaving the agent to infer usage from the name and description alone.

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

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states that the title is discarded after the call, hinting at statelessness, but omits whether network access occurs, what happens on failure, or any side effects. This is insufficient for a 9-parameter tool.

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 wasted words, earning credit for conciseness. However, it is under-specified to the point of being unhelpful, so the structure is minimal but not effectively informative.

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

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

For a tool with 9 parameters, no output schema, and no annotations, the description is grossly incomplete. It does not explain return values, which parameter to use, or how the check is performed. An agent cannot correctly invoke this tool based on the provided information.

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

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

Schema coverage is 100% because every parameter has a description, but those descriptions are generic and copied across tools (e.g., 'discarded after the shape check'). The tool description adds no clarity about which parameter is the Wikipedia title, so the schema does not effectively document the actual input for this tool.

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

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

The description states a specific verb ('Check') and resource ('Wikipedia title'), but the input schema contains nine unrelated parameters (ref, url, city, etc.) with no indication of which one holds the title. This ambiguity fails to differentiate the tool from sibling shape-checkers like file-path-ok or browser-url-ok.

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

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention any conditions, prerequisites, or exclusions, leaving the agent to guess.

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