Unix epoch seconds

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

With no annotations provided, the description carries the full burden and adds one useful disclosure: 'Page content is not stored.' However, it omits the tool's other behaviors implied by the schema — JSON validation and timezone checks — and says nothing about network fetching, failure modes, 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?

Two short sentences with the main function front-loaded and the privacy-related constraint placed second. Nothing is wasted, though the description could better earn its place by covering the JSON and timezone capabilities.

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 4 heterogeneous optional parameters with no output schema and no annotations, yet the description only addresses URL citation. An agent would be blindsided by json and zone parameters, and there is no mention of what happens when these are supplied.

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

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

Schema description coverage is 100%, so the schema already documents all four parameters. The tool description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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

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

The description states a specific verb and resource: 'Return host, scheme, and HTTP status for a URL.' This is clear and actionable. It does not explicitly differentiate from siblings like normalize-url or status-catalog, but the core function is unambiguous.

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

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

No guidance is given on when to use this tool versus alternatives. The description never mentions normalize-url, status-catalog, or any other sibling, and there is no exclusion criteria or recommended 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 provided, the description carries the full burden. It discloses a privacy-relevant behavior ('No identifiers are retained') but does not mention side effects, rate limits, or whether operation is read-only. The privacy statement is useful, but other behavioral aspects are left undisclosed.

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

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

The description is two short sentences with no fluff. The core purpose is front-loaded and the privacy note is brief and relevant.

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 4 optional parameters and no output schema, and the description doesn't explain what 'classified' means or what the output looks like. An agent would not know what to expect from the result or how the parameters influence it. This is a significant gap for a tool that appears to be a checker.

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

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

Schema description coverage is 100%, so the schema already documents each parameter. The description adds no extra meaning beyond the schema fields; it doesn't clarify how the parameters relate to classification or whether they are alternatives or combined. Baseline 3 is appropriate because the schema does the heavy lifting.

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 ('Show how this request is classified') and a key behavioral constraint ('No identifiers are retained'). It distinguishes itself from siblings by implying classification rather than citation or normalization, though it doesn't explicitly name any alternative.

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 the siblings like citation or validate. It does not state preconditions or scenarios where this tool is preferred, so an agent has little help in choosing among the many sibling 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 present, so the description carries the full burden of behavioral disclosure. It only states the operation and a negative scope; it does not mention what the tool does with URL, JSON, or timezone inputs, whether it makes network calls, what it returns, or whether it is purely local.

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 and a clear front-loaded verb. It is concise and readable, though somewhat under-specified for a tool with four optional parameters.

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

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

With no output schema and four seemingly unrelated optional parameters, the description is incomplete for an agent deciding how to invoke the tool. It does not explain how url, json, or zone relate to splitting a hostname, nor what output or behavior to expect.

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 covers 100% of parameters with descriptions, so the baseline is 3. The tool description adds no parameter semantics and does not reconcile the 'hostname' focus with the url, json, and zone parameters, but the schema itself is sufficient for basic parameter-level 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 names a specific verb and resource: 'Split a hostname into labels'. It also adds a clear boundary: 'without WHOIS or ownership data.' It does not explicitly differentiate from siblings like normalize-url or citation, but the core purpose 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?

There is no guidance on when to use this tool versus sibling tools such as normalize-url or citation. The negative scope 'without WHOIS or ownership data' hints at a limitation, but it does not explain when to choose this tool or what inputs are appropriate in different scenarios.

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 reveals only that the names are 'common' and intended 'for clock calls,' but says nothing about output shape, whether parameters are accepted, or why the schema includes url, host, json, and zone. For a tool with four optional parameters, this is a notable transparency gap.

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

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

The description is a single, short sentence with no filler or redundant wording. It could be more actionable by adding an explicit verb, but it is efficient and front-loads the core subject.

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 output schema, no annotations, and four optional parameters, the description is too sparse. It does not explain how to invoke the tool, what the response looks like, or why the listed parameters exist. An agent would struggle to know whether to pass a zone or simply call with no arguments.

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 and does not indicate which parameter, if any, should be supplied to obtain the timezone names. It neither clarifies nor contradicts the schema, so the baseline holds.

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 identifies the tool's resource and scope: it provides common IANA timezone names for clock calls. This clearly separates it from computational siblings like timezone, unix-now, and utc-time. However, it lacks an explicit verb such as 'lists' or 'returns,' so the action is implied rather than stated.

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

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

The phrase 'for clock calls' gives a clear context for when this tool is relevant, but it does not explicitly say when not to use it or name alternatives. An agent can infer that this is the source for IANA zone names, but there is no direct guidance on choosing between this and the sibling timezone-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?

With no annotations provided, the description carries the full burden. It discloses a read-only network fetch of a public resource and that the return is restricted to counts. However, it does not state error behavior for missing robots.txt (404 vs empty), redirect handling, rate limits, or the exact structure of 'group counts.'

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 nine-word sentence that leads with the verb and states the core behavior and output scope. Zero filler; 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?

The tool has 4 optional parameters, no required parameters, no output schema, and no annotations, yet the description only covers high-level behavior. Missing are which parameter is the fetch source, the return shape of 'group counts,' and edge-case behavior. This is insufficient for an agent to invoke the tool reliably.

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

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

Schema coverage is 100%, so the baseline is 3, but the schema descriptions appear mismatched with the stated purpose: 'HTTPS URL to normalize or cite,' 'JSON text to validate; discarded after the check,' and 'IANA timezone name' do not obviously relate to fetching robots.txt. The description adds no mapping between url/host and the fetch target, leaving the agent unable to determine how to invoke 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 states a specific verb and resource: 'Fetch a public robots.txt and return group counts only.' The 'only' constraint scopes the output and distinguishes it from tools that return full robots.txt content. Minor gap: 'group counts' is undefined jargon, and there is no explicit differentiation from the sibling 'citation,' though the difference is self-evident.

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

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

No guidance is given about when to use this tool versus alternatives. The only implicit signal is 'group counts only,' which hints it is for lightweight checks rather than full-content retrieval, but there is no explicit when/when-not statement or reference to sibling 'citation.'

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 transparency burden. It does disclose one concrete behavioral trait: query strings and fragments are dropped from the returned result. But it does not explain behavior for the other input parameters (e.g., that JSON text is 'discarded after the check') and says nothing about invalid URLs, required HTTPS, or whether any state changes occur, leaving transparency 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?

The text is very brief and front-loaded, with the primary behavior stated in the first sentence and an essential normalization rule in the second. There is no wasted wording. However, given the schema's four parameters and the important sibling-tool context, the two-sentence length feels slightly underspecified for the actual tool surface.

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 only complete for a URL-only tool; it fails to address three of the four schema parameters and does not explain how they relate to URL normalization. Since there is no output schema and no annotations, the description is the only source of context, and it is inadequate for correct invocation beyond a plain URL input.

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 useful meaning for the url parameter by defining the normalized output and the dropping rule, but it adds no semantic value for host, json, or zone, and does not clarify why they are accepted alongside a URL. It neither raises nor lowers the score from the schema-driven 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 uses a specific verb ('Return') and names the resource (URL) and the expected outputs (origin, host, path) plus the transformation (query/fragment dropped), making the core purpose clear. However, it never explains what the host, json, and zone input parameters are for, so the stated purpose does not fully align with the 4-parameter schema and the tool's actual scope remains ambiguous.

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

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

The description gives no when-to-use guidance or explicit comparison to sibling tools like validate-json, inspect-robots, or utc-time. The only implicit usage is 'normalize a URL,' which is not enough for an agent to confidently decide between this and its siblings, especially because the schema contains json and zone parameters that overlap with other tool names.

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

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

No annotations are provided, so the description carries the full disclosure burden. It only says the catalog is 'short' and about HTTP status codes; it does not state whether this is a read-only lookup, how optional parameters are handled, or what the response looks like.

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

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

The description is a single short sentence with no filler or redundancy, and the core subject is front-loaded. It is concise, though the brevity comes at the cost of needed context.

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

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

With no annotations, no output schema, and four optional parameters whose relationship to the tool is unexplained, a one-sentence description is not enough for an agent to call this tool confidently. Return format, optionality semantics, and use case are all missing.

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 already has an individual description and the baseline is 3. The tool description adds no parameter-level meaning and fails to connect url/host/json/zone to the catalog, but it does not actively misdescribe them.

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 identifies a clear resource ('common HTTP status codes') and a tool type ('catalog'), so an agent can infer it returns status-code information. However, it lacks an action verb, and the input schema parameters (url, host, json, zone) are unrelated to a status-code catalog, which muddles the intended operation.

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, what inputs are appropriate, or how it differs from sibling tools. The sibling list contains no obviously related alternative, so an agent has no basis for selecting this tool over another.

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 implies a read-only lookup but does not state that passing url, host, or json would be ignored or inappropriate, nor does it describe output format or edge cases like invalid zone names.

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 efficient sentence and is front-loaded with the core behavior. However, it is so terse that it omits essential disambiguation about which schema parameter to use, making brevity a liability here.

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 a schema polluted with unrelated parameters and no output schema, the description is far from complete. An agent cannot reliably determine the correct invocation — it needs explicit direction that only 'zone' is relevant and some indication of the return format.

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%, three of the four parameter descriptions (url: 'HTTPS URL to normalize or cite', host: 'Public hostname', json: 'JSON text to validate; discarded after the check') describe functionality unrelated to a timezone tool. The description only loosely maps to the zone parameter and does nothing to clarify that the other parameters are extraneous.

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 'Current time in a named IANA timezone' states a specific result and resource — it clearly identifies what the tool does. However, it does not differentiate itself from siblings 'unix' and 'utc', which are also time-related, so an agent must infer the 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?

No guidance is given for when to use this tool versus its time-related siblings. The mismatched schema — containing url, host, and json parameters that belong to other tools — makes it harder, not easier, for an agent to figure out which parameters apply to a timezone lookup.

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

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

With no annotations provided, the description carries the full burden of disclosing behavior, but it only names a data format. It does not state that the tool returns the current time, whether it accepts inputs, whether it has side effects, or what the output structure looks like.

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 and free of fluff, which is concise, but it is under-specified rather than appropriately sized for a tool with four parameters. A single noun phrase does not provide enough structure for reliable tool selection and 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?

Given the lack of annotations, lack of an output schema, four unrelated-looking parameters, and a sibling set full of time and URL utilities, 'Unix epoch seconds' is far from complete. The agent cannot determine the return format, parameter semantics, or when this tool is the right choice.

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 of the four parameters already has a documented meaning. However, the description adds no clarification about how 'url,' 'host,' 'json,' or 'zone' relate to 'unix-now,' leaving the parameter-purpose connection 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 'Unix epoch seconds' identifies the subject matter but lacks a verb stating what the tool actually does, such as 'get' or 'convert.' Combined with the name 'unix-now,' an agent can guess it returns the current Unix timestamp, but the description itself is a noun phrase rather than an explicit operation.

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

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

There is no guidance on when to use this tool versus alternatives like 'utc-time' or 'timezone.' The description provides no context, prerequisites, or exclusions, so an agent has little help deciding which sibling tool fits the 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?

With no annotations provided, the description carries the full burden of behavioral disclosure, and 'Current UTC timestamp' discloses only that the operation is a benign read. It reveals nothing about return format, timezone resolution, or why the schema exposes url, host, json, and zone parameters, which makes the actual behavior opaque and potentially 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 short phrase with no wasted words and the key output (UTC timestamp) is front-loaded. It is slightly under-specified, but as a concise statement it is efficient and readable.

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

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

The description is severely inadequate for an agent to invoke this tool correctly: it claims a no-argument timestamp operation while the schema presents four unrelated optional parameters, there is no output schema, and no guidance on parameter relevance. The mismatch between the description and schema makes correct usage essentially unknowable.

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%, which would normally warrant a baseline of 3, but the parameter descriptions describe a URL/timezone/JSON-validation tool, not a timestamp tool. The description adds zero parameter context and fails to reconcile the four unrelated optional parameters with the stated purpose, leaving an agent unable to determine whether any of them affect the result.

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

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

The description 'Current UTC timestamp' states a specific verb and resource, so the intended behavior is nominally clear. However, it does not distinguish itself from the sibling tool 'unix-now', which likely serves a nearly identical purpose, and it is inconsistent with the input schema, which lists url, host, json, and zone parameters that have nothing to do with reading a UTC timestamp.

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 closely related sibling 'unix-now', nor any mention of use cases, prerequisites, or exclusions. An agent must guess which timestamp tool 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?

The statement 'The body is discarded' is a useful behavioral disclosure, indicating the input is not stored or persisted. However, no annotations exist, and the description does not mention what happens with invalid JSON (e.g., error vs. false return), return format, or any side effects beyond discarding the body.

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 filler. The core purpose is stated first, and the important behavioral note follows. 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?

While the tool appears simple, there is no output schema and zero annotations, yet the description omits the result/return behavior, error handling, and does not clarify which parameters are relevant to this tool. The presence of unrelated parameters (url, host, zone) without explanation leaves an agent with significant ambiguity. Given the low complexity, more completeness would be expected.

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 the term 'body' and reinforces the discarding behavior, aligning with the 'json' parameter's schema description. However, it does not explain the role of the other schema parameters (url, host, zone), which appear unrelated to JSON validation and could confuse an agent.

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

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

The description clearly states a specific action and resource: 'Check whether a body is valid JSON.' This is unambiguous and the tool name reinforces it. However, it does not explicitly distinguish itself from sibling tools or mention how it differs from any other validation-related tool.

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

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

The description clearly implies when to use the tool (when you need to validate JSON), but it provides no explicit guidance on when not to use it or what alternatives might be better. There are no usage exclusions or comparisons to sibling tools.

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