Fahrenheit to Celsius

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

With no annotations, the description carries the full burden. It discloses that page content is not stored, which is a useful behavioral trait. However, it does not mention other aspects like whether the URL is fetched live, rate limits, authentication requirements, or error behavior, so coverage is partial.

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

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

Two sentences with no filler. The core purpose is front-loaded, and the privacy note is concise. Efficient and well-structured.

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

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

The description is incomplete for a tool with four parameters. It explains only the URL behavior but leaves host, json, and zone unexplained, creating ambiguity about their purpose. With no output schema, the description should clarify all parameters and return values, which it fails to do.

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 does not add meaning beyond the schema; it only mentions the URL-related outputs, not the roles of host, json, or zone parameters, which remain unexplained.

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 host, scheme, and HTTP status for a URL, which is a specific verb+resource. However, it does not explicitly differentiate from sibling tools like normalize-url or status-catalog, though the combination of three outputs is somewhat distinctive.

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 its siblings. It does not mention any conditions, prerequisites, or scenarios where this tool is preferred, leaving the agent to infer usage context.

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

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

Without annotations, the description carries full responsibility for disclosing behavior. It only mentions that identifiers are not retained, but does not state whether the tool modifies data, performs lookups, or returns any specific result. The behavioral scope is entirely unclear.

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, consisting of only two short sentences, and is front-loaded with the main verb phrase. It avoids unnecessary length, though its brevity comes at the cost of meaningful content.

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

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

The tool lacks any output schema or description of the classification result, and the input parameters are not explained in relation to the tool's operation. An agent would be unable to infer the expected inputs, outputs, or side effects, making the definition 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?

All four parameters have descriptions, so schema coverage is 100%, but the descriptions are generic and not tied to the tool's purported classification function. For example, 'url' is described as 'HTTPS URL to normalize or cite' which hints at unrelated capabilities and adds confusion rather than clarifying how the parameter is 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 'Show how this request is classified' but does not specify what classification means, what inputs are expected, or what the output looks like. It is vague and fails to distinguish the tool's purpose from siblings like 'validate-json' or 'normalize-url'.

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

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

No guidance is provided on when to use this tool versus alternative tools. The description gives no context for the intended use case or scenario, leaving the agent without direction on selection.

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

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

With no annotations, the description carries the full burden of explaining behavior, but it only says 'split a hostname into labels' and what it does not do. It does not mention return format, error behavior, or side effects.

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

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

The description is short and front-loaded with the main action, but the misleading negative clause and lack of essential parameter information reduce 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?

The definition is incomplete for an agent to call it correctly. The parameter names and descriptions conflict with the stated purpose, and no output schema or usage context is provided.

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 parameters are clearly mismatched: 'url' is described as an HTTPS URL to normalize, 'json' as JSON text to validate, and 'zone' as an IANA timezone. These descriptions appear copied from other tools and do not relate to splitting a hostname into labels.

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 splits a hostname into labels, which is a specific action with a clear resource. However, it does not clarify how this differs from sibling tools like normalize-url or status-catalog, and the negative phrase 'without WHOIS or ownership data' adds 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 about when to use this tool versus alternatives. The description omits any context for choosing domain-shape over normalize-url or other related 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, and the description gives no indication of side effects, permissions, or failure behavior. The severe mismatch between the description and the schema further obscures what the tool actually does when invoked.

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, which is concise, but it omits essential information needed to invoke the tool correctly. The brevity here is a drawback rather than a strength because it leaves the schema mismatch unexplained.

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 context is incomplete: the description and schema are contradictory, no output schema is defined, and no usage or side-effect information is provided. An agent would not be able to reliably select or call this tool based on the given information.

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

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

The schema parameters are individually described but are entirely unrelated to Fahrenheit-to-Celsius conversion. There is no temperature parameter, and the description does not explain how url, host, json, or zone relate to the stated purpose.

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

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

The description 'Fahrenheit to Celsius' clearly states a conversion purpose, but the input schema contains unrelated parameters (url, host, json, zone) that do not support any temperature input. This creates confusion about what the tool actually does.

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

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

There is no guidance on when to use this tool versus alternatives. The sibling tools include timezone and validation utilities, but nothing clarifies whether f-to-c should be used for temperature conversion or something else entirely.

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

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

No annotations are provided, and the description does not disclose any side effects, data transformations, or whether the tool is read-only or mutating. The actual behavior is entirely opaque, making it impossible to predict the tool's impact.

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 brief, which could be seen as concise, but it fails to convey essential information. It is not front-loaded with a clear action or purpose; instead, it is a vague fragment. A single sentence that is meaningful would be better than a short but empty phrase.

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

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

The tool has no output schema and no additional context, and the description is so sparse that the agent cannot determine what the tool does, how to call it, or what to expect. Given the apparent mismatch between the described timezone names and the URL/host/json parameters, the description is completely inadequate for safe and effective use.

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

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

The description does not explain how the parameters (url, host, json, zone) relate to the tool's purpose. The schema lists them, but the description adds no semantic context, leaving the agent to guess which parameters are relevant and how they should be populated. The description provides essentially no value beyond the raw 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 'Common IANA timezone names for clock calls' is a noun phrase, not a verb phrase. It does not state what action the tool performs, whether it returns a list, validates a timezone, or converts something. The mention of 'clock calls' is cryptic and the purpose is completely 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?

The description gives no indication of when to use this tool versus alternatives like 'timezone' or 'utc-time'. There is no mention of scenarios, prerequisites, or comparative guidance.

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

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

With no annotations present, the description carries the full burden of disclosing behavior. It only mentions fetching and returning counts, but does not explain error handling, rate limits, or any side effects. This is insufficient 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 concise sentence, but it omits essential information about how parameters contribute to the task. It is too sparse to be fully useful, yet it is not overly verbose.

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

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

The tool description is inconsistent with its parameters, making it incomplete. There is no explanation of how 'url', 'host', 'json', or 'zone' relate to fetching robots.txt, and no output schema is provided. This creates significant ambiguity for an agent.

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

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

The parameter descriptions are clearly copy-pasted from other tools, such as 'JSON text to validate' and 'IANA timezone name', and bear no relation to fetching robots.txt. The schema covers all parameters, but the descriptions are misleading and do not explain how they affect the group counts.

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 'Fetch' and resource 'robots.txt', and specifies the output as 'group counts only', which gives a clear purpose. However, it does not differentiate from sibling tools, but the core action is understandable.

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

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

The description provides no guidance on when to use this tool versus alternatives like 'normalize-url' or 'validate-json'. It lacks any contextual cues or scenarios that would help an agent decide to invoke 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 mentions one behavioral aspect (query and fragment are dropped) but does not disclose other potential effects such as side effects, errors, or permissions. With no annotations, this minimal information leaves much unspecified.

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

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

The description is extremely concise, using one sentence to convey the core functionality. No unnecessary words or redundancy.

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

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

The description is incomplete due to the mismatch between the tool's purpose and the parameter list. It does not explain the role of host, json, or zone, leaving the tool's actual behavior unclear.

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 parameters (url, host, json, zone) are largely inconsistent with the tool's stated purpose. 'json' and 'zone' have descriptions irrelevant to URL normalization, and 'host' is ambiguous. The description does not clarify how these parameters relate to the tool's function.

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

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

The description clearly states the tool's purpose: to return origin, host, and path from a URL while dropping query and fragment. It uses a specific verb and resource, though it does not explicitly differentiate from sibling tools.

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

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

No guidance is provided about when to use this tool versus alternatives. The description only explains what the tool does, not when it is appropriate 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?

No annotations are provided, and the description does not mention side effects, read-only nature, or any behavioral traits. Since it is described as a catalog, it is likely read-only, but this is not explicitly stated.

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

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

The description is concise but overly vague, and it fails to clarify how the parameters relate to HTTP status codes. It is short but not sufficiently 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?

The description is incomplete and confusing due to the mismatch between the tool purpose and the parameters. An agent would not know how to invoke this tool correctly based on the given information.

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

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

The parameters (url, host, json, zone) are completely mismatched with the tool's stated purpose of an HTTP status code catalog. The schema descriptions are generic and appear copied from other tools, providing no meaningful explanation 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 the tool provides a short catalog of HTTP status codes, which is a clear purpose. However, the parameter names (url, host, json, zone) are unrelated to HTTP status codes, creating confusion about the tool's actual function.

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

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

The description gives no guidance on when to use this tool versus alternatives. The sibling tools (e.g., validate-json, normalize-url) have overlapping parameter names, but no distinction is explained.

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 'Current time' and does not describe output format, error behavior for invalid zones, or whether the operation is read-only or network-dependent. This is minimal for a simple read tool but not sufficient without annotations.

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

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

The description is one short sentence with no filler and front-loads the core behavior. However, it is so terse that it omits usage guidance and parameter disambiguation.

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 no annotations, no output schema, and a schema containing unrelated optional parameters, the description is too thin. It does not state which parameter to pass, what the response looks like, or how it differs from utc-time. An agent cannot confidently invoke it correctly.

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

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

The schema documents all four parameters, but three of them (url, host, json) are unrelated to timezone and appear to belong to sibling tools. The description only reinforces 'IANA timezone name' for zone and does not clarify that the other parameters are irrelevant or ignored, creating confusion despite high schema coverage.

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

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

The description states the tool returns the current time for a named IANA timezone, which is specific enough to distinguish it from utc-time and iana-zones. It lacks an explicit imperative verb, but the resource and scope are clear.

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

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

No guidance is given about when to use this tool versus utc-time or iana-zones, and there is no mention of required inputs or fallback behavior. The intended context is implied but never explicitly stated.

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

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the output ('timestamp') but omits details like whether parameters are optional, if any side effects occur, or the exact format returned. This is sparse but not misleading.

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

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

The description is a single, concise sentence with no filler. It is appropriately short, though it lacks structural guidance on how to invoke the tool.

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 presence of four parameters and no output schema, the description is inadequate. It does not explain why those parameters exist or how they relate to the tool's purpose, leaving significant gaps for an agent trying 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter information, and the parameters (url, host, json, zone) seem unrelated to fetching a UTC timestamp, creating potential confusion. The description does not bridge this gap, but the baseline applies.

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

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

The description clearly states the tool returns the current UTC timestamp, using a specific verb and resource. However, it does not distinguish itself from sibling tools like 'timezone' or 'iana-zones', which could overlap in purpose.

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

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

There is no guidance on when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or related tools, leaving an agent to infer usage.

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

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

The description discloses one behavioral aspect: 'The body is discarded.' However, it does not clarify whether the tool performs a read-only check, what it returns, or any side effects beyond discarding the input. The lack of annotations leaves most behavioral details undocumented.

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

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

The description is very concise, using only two sentences. It is reasonably well-structured, but the extreme brevity and contradictory parameters reduce the effectiveness. Still, it does not waste words.

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

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

The tool is highly incomplete for an agent. There is no output schema, no usage context, and the parameter semantics do not align with the described purpose. The agent would have no way to know what to provide or what to expect as a result, especially given the unrelated parameters.

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

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

The schema descriptions for parameters are misleading relative to the tool's stated purpose. While the 'json' parameter is described as 'JSON text to validate', other parameters like 'url', 'host', and 'zone' are described for unrelated purposes (normalize, cite, timezone). The description adds no clarification and the parameter set appears inconsistent with the tool's function.

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

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

The description clearly states the action: 'Check whether a body is valid JSON.' It also explains the outcome that the body is discarded. However, the stated purpose conflicts with the parameter set (url, host, zone), which introduces ambiguity about the actual functionality.

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

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of conditions or scenarios that would make this tool preferable, nor any criteria to distinguish it from sibling tools.

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