Weekday vs weekend

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

With no annotations, the description must disclose behavior itself, but 'Weekday vs weekend' reveals no side effects, return value, required inputs, or edge cases. The input schema's mentions of URL, host, JSON, and timezone make the actual behavior even more 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 short but this is under-specification rather than efficient conciseness. Three words provide no actionable content and fail to earn their place as a tool definition.

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 output schema, no annotations, and a description that does not state the result or how inputs relate. An agent could not confidently select or invoke this tool correctly.

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

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

Schema description coverage is 100%, which sets the baseline at 3. The description adds no parameter meaning, and the schema fields (url, host, json, zone) appear disconnected from the 'weekday vs weekend' concept, but the individual parameter descriptions are present to 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 'Weekday vs weekend' is a fragment with no verb, no explicit action, and no resource. It merely restates the concept implied by the tool name 'bussiness-day' rather than explaining what the tool 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 or when to prefer a sibling such as timezone, utc-time, or iana-zones. The description does not state any context, exclusions, or alternatives.

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

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

No annotations are provided, so the description carries the behavioral transparency burden. It does disclose that page content is not stored, which is a meaningful privacy and side-effect guarantee. However, it does not state whether the tool fetches the URL, follows redirects, requires authentication, or has rate limits, leaving behavioral 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 description is two short sentences with the primary purpose front-loaded. The second sentence adds a valuable behavioral note about content not being stored. There is no filler, repetition, or unnecessary detail.

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

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

The description is adequate for the basic URL case but not fully complete for the tool's actual parameter surface: it omits the roles of `host`, `json`, and `zone`. With no output schema, the return value is described only at a high level, and the no-storage note is helpful but does not fully compensate for the missing multi-parameter 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 because the schema already documents all four parameters. The description only adds context for `url` and does not clarify how `host`, `json`, and `zone` relate to the citation operation. It neither significantly improves on nor contradicts the schema, but leaves potential ambiguity for an agent deciding which parameter to supply.

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 ('Return') and a specific resource ('host, scheme, and HTTP status for a URL'), making the tool's core function immediately clear. It is distinguishable from siblings like normalize-url, validate-json, and status-catalog because it returns citation metadata for a URL rather than transforming URLs, validating JSON, or listing status codes.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The intended use is implied by the purpose statement: call this when you need host, scheme, and HTTP status for a URL. However, the description does not help an agent choose between this and sibling tools such as normalize-url or status-catalog.

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

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

With no annotations, the description carries the full burden. It does disclose one meaningful behavioral trait: 'No identifiers are retained.' However, it does not clarify whether the operation is read-only, whether URLs are fetched, or what side effects may occur, leaving gaps.

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

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

The description is short and front-loaded, with no fluff. However, it is so sparse that it borders on under-specification; the first sentence earns its place by stating a purpose, but that purpose remains too ambiguous to be fully useful.

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 no output schema, no annotations, four optional parameters, and many sibling tools, the description is not complete enough for an agent to invoke the tool confidently. It does not explain what classification is returned, how the inputs relate, or when this tool is preferable to alternatives.

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 per-parameter meaning beyond the schema; the privacy note is general and does not clarify how url, host, json, or zone are used in classification.

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

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

The description says 'Show how this request is classified' but never explains what classification means, what the result looks like, or what 'compatibility' refers to. It is vague rather than a specific verb+resource statement and does not distinguish it from siblings like validate-json or domain-shape.

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

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

No guidance is given about when to use this tool versus the siblings. The schema lists four optional inputs, but the description does not say which inputs should be provided together or what kind of request is expected.

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 reveals only one negative trait (no WHOIS/ownership data) and says nothing about side effects, return format, or behavior on non-hostname inputs. The schema's json parameter ('discarded after the check') sits uneasily beside a hostname-splitting purpose, and the description does nothing to resolve this tension.

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, front-loaded with the action ('Split a hostname into labels') followed by a scope qualifier. Every word earns its place and there is no redundancy or 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?

With 4 unrelated parameters, no output schema, and no annotations, an agent cannot tell what the 'labels' output looks like, which parameters to populate, or whether full URLs are accepted. The mismatch between a hostname-splitting purpose and json/zone parameters leaves the tool underspecified for reliable invocation; a short example or input-form clarification would materially help.

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; per the rubric the description need not re-explain parameters. It adds a coarse hint that hostname-shaped inputs (host or url) are relevant, but it provides no mapping for the json and zone parameters, and its single-purpose framing partially conflicts with the multi-purpose schema. This nets out at baseline.

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

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

The description states a specific verb and resource ('Split a hostname into labels') plus a negative scope ('without WHOIS or ownership data'), making the core action clear. It is distinguishable from siblings like normalize-url and citation, though the contrast is slightly abstract since no listed sibling actually provides WHOIS data. The broad 4-parameter schema (url, host, json, zone) muddies which inputs this tool actually consumes, which keeps this from a 5.

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

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

The description offers no guidance on when to use this tool versus alternatives, and no indication of the expected input form (bare hostname vs full URL). The negative clause implies a contrast with ownership-enrichment tools but never names one or states the selection condition, leaving the when-to-use decision entirely 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool returns a list, validates a zone name, or relies on any input parameters. The description is not misleading, but it reveals almost nothing about runtime 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 single sentence is concise and free of filler, which is good, but it is under-specified. It reads more like a heading or tagline than a functional tool description, and the brevity reduces the agent's ability to use it correctly.

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 and no output schema, the description should clearly explain what the tool returns and how the optional parameters are used. It does not mention return values, and the schema's url, host, and json parameters appear disconnected from the timezone-names focus, leaving significant ambiguity.

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

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

Schema description coverage is 100%, so the baseline is 3. The description's reference to timezone names maps loosely to the 'zone' parameter, but it adds no extra meaning about url, host, json, or the exact role of zone beyond what the schema already says.

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 resource as common IANA timezone names and hints at the clock-call context, but it lacks an action verb such as 'list', 'return', or 'validate'. It adds some meaning over the bare tool name but does not clearly distinguish itself from sibling tools like timezone or utc-time.

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

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

Only the phrase 'for clock calls' gives a faint usage context. There is no explicit when-to-use guidance, no mention of alternatives, and no exclusions, so an agent cannot confidently decide when to choose this tool over related siblings.

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

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

With no annotations, the description must carry the behavioral disclosure burden. It does reveal that this is a public network fetch and that the result is limited to group counts, but it does not mention failure modes, side effects, or behavior when no host/URL is supplied.

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?

One sentence with no filler; 'Fetch a public robots.txt' is front-loaded and 'group counts only' adds an important scope constraint. Every clause 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?

For a tool with four optional parameters, no output schema, and no annotations, this description is too thin. It omits which parameter identifies the target site, what the 'group counts' structure looks like, and how errors or the absence of a robots.txt are handled.

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

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

Although the input schema has descriptions for all parameters, those descriptions appear copied from other tools ('URL to normalize or cite', 'JSON text to validate', 'IANA timezone name') and do not align with the robots.txt task. The description provides no mapping between the fetch operation and the four parameters, leaving the agent unable to confidently choose the correct one.

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 ('Fetch'), a concrete resource ('public robots.txt'), and a clear output scope ('group counts only'). This clearly differentiates it from sibling tools like normalize-url and validate-json, none of which mention robots.

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 select this tool over alternatives, and there are no prerequisites or explicit exclusions beyond the word 'only'. It states the operation but not a decision rule, so an agent must infer the appropriate use case.

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

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

With no annotations, the description carries full behavioral disclosure burden. It does disclose a meaningful behavior (dropping query and fragment), but it says nothing about input validation, error behavior, or what happens when the other accepted schema parameters (host, json, zone) are supplied, which is especially confusing given the mismatch between the description and the schema.

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

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

Two short sentences, front-loaded with the main purpose and immediately followed by the critical drop behavior. Every word earns its place; there is no fluff.

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 schema parameters, no annotations, and no output schema, yet the description only addresses URL normalization. It does not specify the return structure or explain how the other parameters fit, so an agent cannot fully predict tool behavior across all valid inputs.

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

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

Schema description coverage is 100%, so a baseline of 3 applies. The description adds useful behavior-level meaning for the url parameter, but it does not clarify how host, json, or zone relate to the stated behavior, leaving their purpose ambiguous beyond the schema descriptions.

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

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

The description states a clear operation ('Return origin, host, and path for a URL') and adds a precise behavioral detail (query and fragment are dropped). It is specific but does not explicitly distinguish itself from sibling tools like domain-shape or citation.

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

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

The description implies the tool should be used when a caller needs origin, host, or path rather than the full URL. However, it provides no explicit guidance on when to choose this tool over siblings, nor any exclusions or alternative routing.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about side effects, output format, parameter handling, or whether this is a read-only lookup. The noun phrase 'catalog' implies a static list, but that is inference, not disclosure.

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, but it is under-specified rather than appropriately concise. Seven words cannot cover the tool's purpose, parameters, and output expectations.

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 optional parameters, no annotations, and no output schema, this description is severely inadequate. It does not state what action the tool performs, how parameters affect the catalog, what it returns, or when to use it. An agent has almost no chance of invoking 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 meaning beyond the schema and fails to explain how the four unrelated parameters (url, host, json, zone) relate to an HTTP status code catalog, but the schema itself at least documents each parameter.

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

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

The description 'Short catalog of common HTTP status codes' is essentially a restatement of the tool name 'status-catalog'. It adds only the qualifiers 'short' and 'common HTTP' but lacks a verb or action, so an agent cannot tell what invoking the tool actually does or how it differs 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?

There is no guidance about when to use this tool versus alternatives. The description never mentions use cases, filters, or related sibling tools, leaving an agent without any context for selection.

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

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

No annotations are provided, so the description carries the full disclosure burden. It only says 'Current time in a named IANA timezone' and does not mention output format, behavior for invalid zone names, whether the operation is read-only, or any network/time-source dependencies.

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

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

The description is a single, front-loaded sentence with no wasted words. It communicates the core operation efficiently.

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

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

With no output schema, no annotations, and a confusing four-parameter schema, the definition is not complete enough for an agent to invoke the tool correctly. The unrelated parameters and lack of parameter-selection guidance create a significant gap.

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 technically 100%, but the descriptions for url, host, and json are clearly unrelated to a timezone tool ('HTTPS URL to normalize or cite', 'JSON text to validate'). The description reinforces that zone is a timezone name but does not tell the agent whether the other parameters are ignored, optional, or invalid 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 clearly states the tool returns the current time for a named IANA timezone, which distinguishes it from siblings like utc-time and iana-zones. However, it is terse and does not clarify how the unrelated parameters in the input schema fit into this purpose.

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

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

The intended use is implied: call this when you need the current time in a named IANA timezone. There is no explicit guidance about when to prefer utc-time or iana-zones, nor any exclusion criteria.

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

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

With no annotations, the description carries the behavioral burden, but it only names the output. It does not disclose the returned format, precision, or how the four schema parameters (url, host, json, zone) are treated, which is especially confusing because they appear unrelated to a UTC timestamp.

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 and front-loaded, with no wasted words. However, it is under-specified for a tool whose schema lists four optional parameters; a few clarifying clauses would make the extra length worthwhile.

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

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

There is no output schema and no annotations, and the description does not reconcile the schema parameters with the stated function. An agent cannot tell whether to pass zone, whether output is ISO-8601 or Unix time, or whether the other parameters are obsolete, so the definition is incomplete.

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

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

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter-level semantics, and it does not clarify whether the optional parameters are accepted, ignored, or determine output, which would be valuable given the mismatch with the tool's 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 'Current UTC timestamp' clearly states the tool's output as the present UTC time, which is a specific and identifiable resource. It does not explicitly distinguish itself from sibling tools like timezone, so it loses a point for differentiation.

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 timezone, iana-zones, or business-day. The phrase implies it returns the current UTC time but provides no exclusions, prerequisites, or alternative routing.

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

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose one meaningful trait: the body is discarded after the check, implying no persistence. However, it does not state what the tool returns (e.g., a boolean, error, or report) or how invalid JSON is reported, which leaves some agent-facing ambiguity.

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

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

The description is appropriately short and front-loads the purpose and the key side effect in two sentences with no fluff. It loses a point because the ambiguous 'body' versus 'json' wording could have been clarified in the same space.

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

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

With no output schema and no annotations, the description must provide enough for an agent to invoke the tool confidently. It explains the core check-and-discard behavior but omits the return contract, invalid-input behavior, and the role of the unrelated parameters. For a validation tool, this is a meaningful gap.

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

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

Although the input schema has 100% parameter description coverage, three of the four parameters (url, host, zone) are unrelated to JSON validation, and the description refers to 'a body' instead of the 'json' parameter. The description adds no clarification about which parameters are actually used or ignored, so the schema coverage alone does not make the parameter semantics trustworthy.

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

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

王The description states a specific verb ('Check') and resource ('whether a body is valid JSON'), making the core purpose clear. It does not explicitly differentiate from sibling tools, but the name and action are distinct enough. The main ambiguity is that 'body' does not obviously map to the 'json' parameter in the input schema.

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 siblings such as normalize-url, domain-shape, or status-catalog. There is no mention of when not to use it or any alternatives. The agent is left to infer usage solely from the name and minimal description.

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