EAN/UPC digit shape

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

With no annotations, the description must disclose side effects; it only says 'Page content is not stored,' which addresses retention but not network behavior, read-only guarantees, or failure modes. This is insufficient transparency for a tool that fetches URLs and returns HTTP status.

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

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

The description is brief and front-loaded, but it is too sparse for the apparent complexity of four unrelated parameters. The second sentence adds a privacy note but does not help structure the tool's behavior or parameter usage.

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

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

With no output schema, no annotations, and a mismatch between the description and parameters, the agent lacks critical context about return format, parameter combinations, and error behavior. The description is far from complete for reliable invocation.

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

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

Although all parameters have descriptions, they are disconnected from the tool's stated purpose: json is for validation and zone is a timezone, both irrelevant to returning host, scheme, and HTTP status. The descriptions do not explain how these parameters relate to each other or to the tool's core 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 names a concrete action and output ('Return host, scheme, and HTTP status for a URL'), so the primary purpose is somewhat clear. However, the tool name 'citation' and the unrelated parameters (json, zone) make the intended 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?

The description gives no guidance on when to use this tool instead of its siblings, such as normalize-url, status-catalog, validate-json, or timezone. It states what it returns but not the conditions or use cases for choosing 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, so the description carries full responsibility for behavioral disclosure. The only behavioral statement is 'No identifiers are retained,' which addresses privacy but not what the tool does with inputs, whether it is read-only, or what side effects occur. The core behavior (classification) is entirely 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 short sentence, which is under-specified rather than concise. It omits critical information that the agent needs, so the brevity is not a strength. The privacy note is front-loaded but not the actual purpose.

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 four parameters, no output schema, and no annotations, the description is severely incomplete. An agent cannot determine what the tool does, what it returns, or how to use it correctly. The description fails to explain the classification concept or the role of each parameter, making the tool nearly unusable without external knowledge.

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

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

The schema covers 100% of the four parameters, each with a description, so the baseline is 3. The description adds nothing about how these parameters relate to the classification or how they should be combined. It does not compensate for any gaps because there are none in the schema, but it also does not add value 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 'Show how this request is classified' is vague. It does not specify what 'request' means, what kind of classification is performed, or what the output looks like. It also does not differentiate from sibling tools like normalize-url or validate-json, which handle specific inputs. The name 'compatibility' hints at a purpose, but the description itself is not 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?

There is no guidance on when to use this tool versus its siblings. The description provides no context about scenarios, prerequisites, or alternatives. An agent would have no idea whether to pick this over cite, inspect-robots, 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 must disclose side effects and behavior. It implies a pure transformation ('Split') and clarifies what it does not return, but it does not mention read-only status, error behavior, or whether input is stored, so transparency is incomplete.

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 an active verb and a useful negative clarification. It is concise and 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?

With four parameters and no output schema, the description is too sparse. It does not say which parameter is required, how the parameters interact, or what the resulting labels look like, leaving important context 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?

Although every parameter has a schema description, the tool description does not connect 'hostname' to any specific parameter, and url, json, and zone appear unrelated to splitting hostnames. The descriptions read as if copied from other tools, so the parameter semantics are confusing rather than clarified.

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

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

The description states a concrete action ('Split a hostname into labels') and a useful negative scope ('without WHOIS or ownership data'), but it does not clarify which of the four unrelated parameters (url, host, json, zone) should be used, leaving the core purpose somewhat ambiguous.

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

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

There is no guidance on when to use this tool versus sibling tools such as normalize-url or iana-zones. The only comparative hint is the negative phrase about WHOIS/ownership, which is not enough to guide 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. There is no mention of side effects, output format, error behavior, or any processing characteristic. The phrase 'digit shape' gives no operational detail at all.

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

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

The description is short, but this is under-specification, not conciseness. One noun phrase carries no information beyond the tool name and provides no actionable content, so brevity earns no credit.

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 4 parameters, no output schema, and no annotations, the description is completely inadequate. It doesn't explain what the tool returns, how the parameters relate to EAN/UPC digits, or any call prerequisites. Almost everything an agent needs to call it correctly is 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?

Although schema coverage is 100% (all four params have schema descriptions), the parameters (url, host, json, zone) are entirely unrelated to the stated EAN/UPC purpose, and the description adds nothing to bridge that gap. An agent cannot tell which parameter applies to the EAN/UPC check, and the json param's 'discarded after the check' behavior is documented only in the schema, not the description. The description fails to compensate for the mismatch.

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 bare noun phrase 'EAN/UPC digit shape' that essentially restates the tool name 'ean-shape' with no verb. It doesn't state whether the tool validates, generates, or checks EAN/UPC digits, and offers no differentiation from siblings like validate-json or domain-shape. It implies a barcode-format concern but never says what operation it performs.

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 whatsoever on when to use this tool versus the ten siblings. There is no stated context, no mention of alternatives, and no exclusions. An agent has no way to decide between ean-shape and a sibling like validate-json or compatibility.

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 does not explain what the tool returns, whether it performs validation, or any side effects. The single sentence offers no insight into its operational 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 extremely brief—a single clause. While concise, it is under-specified and fails to convey the tool's purpose or usage, making it ineffective rather than efficiently 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?

Given the tool has 4 parameters, no annotations, and no output schema, the description is grossly insufficient. An agent cannot determine what the tool does, how to call it correctly, or what to expect in return. It is almost as incomplete as a tautology.

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 description coverage is 100% (each parameter has a description), the tool description adds nothing about how parameters relate to the tool's purpose. The presence of 'url', 'host', and 'json' parameters alongside 'zone' is unexplained, and the description gives no context to disambiguate their roles. It does not compensate for the schema's lack of functional context.

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 'Common IANA timezone names for clock calls,' which gives a hint that it provides timezone names, but it lacks a clear verb and resource. It doesn't specify what action the tool performs (e.g., list, validate, convert), and it doesn't differentiate 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. The sibling tools include 'timezone' and 'utc-time,' but the description never mentions them or provides 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 provided, the description must disclose behavioral traits. It implies a network fetch and a reduced output, but does not mention error handling, authentication, rate limits, or what happens with invalid inputs. It also fails to explain how the listed parameters (url, host, json, zone) relate to the action, leaving behavior 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 a single, compact sentence with no filler or redundancy. It conveys the core action and output in an efficient, front-loaded manner.

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 four parameters (all optional) and no output schema or annotations, yet the description gives no indication of expected inputs, required fields, return format, or error behavior. The parameter mismatch compounds the incompleteness, leaving an agent without enough information to use the tool correctly.

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

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

Although schema coverage is 100%, the parameter descriptions (e.g., 'HTTPS URL to normalize or cite', 'JSON text to validate') do not align with the stated action of fetching robots.txt. The description adds no clarification on how these parameters are used, and the mismatch suggests either a misleading description or an erroneous schema, making parameter semantics poor.

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 a public robots.txt') and the output ('return group counts only'), making the purpose specific and distinguishable from generic tools. However, it does not differentiate from siblings like citation or normalize-url, and the parameter schema appears unrelated to the stated purpose, which slightly 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, contexts, or conditions where this tool is preferred, nor does it name any sibling tools 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, the description bears full responsibility for disclosing behavior. It does reveal that query and fragment are dropped, which is a useful behavior. However, it omits critical details: what happens for invalid or non-HTTPS URLs, the exact output format, and the role of the other three parameters (host, json, zone) that appear in the schema. This omission is significant because an agent cannot predict how these extra parameters affect execution.

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 (two short sentences) and front-loads the primary action and output. There is no fluff or redundancy. However, it is so brief that it leaves major gaps, but conciseness itself is well-handled—it just sacrifices completeness.

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

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

For a tool with only one relevant parameter (url) but a schema listing four, the description should clarify which parameters are used and which are extraneous. It does not. There is no output schema, so the description should specify the return format (e.g., a string, an object with keys), but it only lists components. The description is insufficient for an agent to call the tool correctly, especially given the confusing extra 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 provides 100% description coverage, so the baseline is 3. However, the description adds no value beyond the schema—it does not even mention the 'url' parameter. More problematically, the description fails to reconcile the presence of 'host', 'json', and 'zone' parameters, which appear irrelevant to URL normalization. An agent cannot determine whether these are accepted, ignored, or required for other modes, creating confusion and reducing clarity beyond what the schema alone provides.

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 (return) and resource (URL), and specifies the output components (origin, host, path) plus a clear behavioral rule (dropping query and fragment). It is distinct enough from sibling tools, though it does not explicitly name alternatives. The presence of unrelated parameters in the schema slightly muddies clarity, but the core purpose 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 like citation or domain-shape. There is no mention of prerequisites (e.g., must be HTTPS, must be a public URL) or conditions under which a different tool would be more appropriate. The description only states what it does, leaving the 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?

No annotations are provided, and the description does not disclose side effects, read-only nature, or any other behavioral details. The tool's behavior remains opaque.

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

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

The description is a single concise sentence without unnecessary words. However, its brevity lacks substantive information, though it does not contain filler.

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

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

The description does not explain what the tool returns (e.g., a list of codes or a specific code) or how it processes the input parameters. With no output schema and no additional context, the tool is incomplete for an agent to invoke effectively.

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

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

While each parameter has a description in the schema (100% coverage), the descriptions (e.g., 'HTTPS URL to normalize or cite') are generic and do not relate to the stated purpose of being an HTTP status code catalog. This mismatch fails to clarify how to use the parameters correctly.

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

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

The description states it is a 'short catalog of common HTTP status codes' but does not specify the exact action (e.g., list, lookup, or return a code). It also does not align with the schema parameters (url, host, json, zone), which are unrelated to HTTP status codes, making the purpose ambiguous.

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

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

There is no guidance on when to use this tool versus alternative tools. No context is provided for appropriate usage 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 disclosing side effects and read-only behavior. 'Current time' implies a non-destructive lookup, but the description does not explicitly state that the tool has no side effects, requires no special permissions, or handles invalid timezone 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 brief and front-loaded, but it omits essential information about the misleading parameters and usage context. A concise description should still clarify the tool's scope; this one leaves critical gaps.

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 practical use: it does not explain why url, host, and json parameters are present, does not describe the output format, and does not state how invalid or unrecognized timezone names are handled. Given the confusing parameter list, an agent would struggle to invoke the tool correctly.

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

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

Although all four parameters have schema descriptions, most are unrelated to the stated purpose. 'url', 'host', and 'json' appear copied from other tools (normalize-url, compatibility, validate-json) and are not explained in the context of timezone lookup. Only 'zone' aligns with the description, and no guidance is given on the other parameters' relevance or expected values.

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 indicates the tool returns the current time for a named IANA timezone, which distinguishes it from the sibling utc-time tool. However, it uses a noun phrase rather than an explicit verb like 'get' or 'retrieve', so the intended 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 description gives no guidance on when to use this tool versus siblings such as utc-time or iana-zones. There is no mention of prerequisites, fallback behavior, or cases where another tool would be more 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?

With no annotations, the description carries the full behavioral burden, but it only states the output and says nothing about whether parameters are accepted, ignored, or rejected. It also fails to disclose the timestamp format (e.g., Unix seconds vs ISO 8601), which is important for correct downstream use.

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

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

The description is a single, front-loaded sentence with no filler. It is appropriately short for a trivial tool, though it would earn a 5 only if it also clarified the ambiguous parameter situation.

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

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

The tool is simple, but the description omits two things an agent needs: the exact output format of the timestamp and whether the four optional input parameters are ignored or meaningful. The mismatched schema makes this incompleteness more damaging, since an agent cannot confidently invoke the tool with the right 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?

Although every parameter has a schema description, those descriptions describe URL, host, JSON, and timezone concepts that are unrelated to a tool returning the current UTC timestamp. The tool description adds no clarification about whether these optional parameters affect the result, creating real ambiguity for an agent deciding whether to pass zone or url.

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 resource and result clearly: a current UTC timestamp. It is distinguishable from the sibling 'timezone' tool by explicitly naming UTC, though it lacks a verb and does not spell out that it returns a timestamp value.

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 instead of related siblings like timezone or iana-zones. The description does not mention exclusions, alternatives, or typical use cases, leaving selection to inference.

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

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

With no annotations, the description carries the burden. It discloses that the body is discarded (implying no side effects), but it does not describe the return format (e.g., boolean, error) or any strictness rules. This is minimal 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?

Two sentences with no filler. The primary action is front-loaded, and the discard behavior is mentioned succinctly. Perfectly sized for a simple validation 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?

The description is missing the expected output (e.g., returns true/false) and does not clarify whether other parameters (url, host, zone) are ignored or relevant. While the tool is simple, an agent might be uncertain about the return value and parameter usage. The schema covers parameter names but not usage 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 the baseline is 3. The description adds little beyond the schema: it uses 'body' to refer to the JSON text, which is already described in the 'json' parameter. No new semantic insight 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 clearly states the action ('Check whether a body is valid JSON') with a specific verb and resource. It is distinct from all siblings, which focus on URLs, zones, and other formats. The term 'body' is slightly ambiguous but likely refers to the 'json' parameter, and the tool name reinforces the 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 provided on when to use this tool versus alternatives. While it is clearly distinct from siblings, there is no mention of scenarios (e.g., validating user input before processing) or exclusions. The description does not help the agent decide if this is the right tool.

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