SSE Accept hint

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Returns connection methods' and 'Task text discarded,' but it does not explain whether the tool makes network calls, whether inputs are validated only, what side effects exist, or how the 'connection methods' are structured. For a tool that likely interacts with external pay-per-call services, this is a significant 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 sentence and technically concise, but it is severely under-specified for a tool with 9 parameters and no other documentation. It omits critical context about parameter usage, return format, and behavior, so the brevity is not a virtue—it's a deficiency. The description is too short to earn a higher score on structure.

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

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

Given the tool has 9 parameters, no output schema, no annotations, and a complex purpose (finding pay-per-call gateways), the description is wholly inadequate. It doesn't explain what 'connection methods' are, how to select parameters, what validation occurs, or what the agent should do with the result. An agent would have no reliable way to call this tool correctly based on the description alone.

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

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

The input schema has 100% coverage, with each parameter described individually (e.g., 'City name for a public weather hint'). The tool description adds little beyond the schema: it doesn't explain how parameters map to tasks like weather, search, or voice. However, the schema descriptions are already informative, so the description doesn't degrade semantics. Baseline 3 is appropriate since 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 verb ('Find') and a resource ('public pay-per-call tool gateway') with examples of tasks (weather, search, scrape, voice), which gives a basic purpose. However, it doesn't clarify what a 'gateway' is or how the input parameters relate to the task, and it doesn't differentiate from the many sibling tools that handle specific tasks directly. The purpose is recognizable but vague.

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 mentions 'for a task such as weather, search, scrape, or voice' which hints at when to use it, but it provides no explicit guidance on when not to use it, what alternatives exist, or which parameters to provide for which task. There is no reference to sibling tools or exclusions, so an agent would have to guess how to invoke it correctly.

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?

Annotations are absent, so the description carries the full burden. It does disclose the return behavior (host, scheme, HTTP status) and the privacy-relevant behavior 'Page content is not stored,' which is useful. However, it does not clarify that the tool likely makes a live HTTP request, how json/zone inputs behave, or whether there are side effects or authorization requirements.

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, both purposeful and front-loaded: the first states the function, the second adds a meaningful privacy guarantee. There is no filler, redundancy, or wasted wording.

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 compensate for a 4-parameter polymorphic input schema, but it covers only the URL mode. It leaves json and zone behavior, output shape, and whether parameters are alternatives or combinable entirely unspecified, making it insufficiently complete for correct invocation.

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

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

Schema description coverage is 100%, so the baseline is 3. The description adds meaning for the url parameter by linking it to the host/scheme/status output, but it adds no clarification for host, json, or zone, which appear disconnected from the stated purpose.

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

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

The description states a specific verb and resource: 'Return host, scheme, and HTTP status for a URL.' This is clear and not a tautology. However, it does not differentiate the tool from the sibling normalize-url, and it ignores the json and zone parameters, which suggest additional capabilities beyond URL 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 provides no when-to-use guidance and no exclusions or alternatives. It never references the sibling tools normalize-url, validate-json, or timezone, nor does it clarify whether url, host, json, and zone are mutually exclusive input modes. An agent must infer usage entirely from the schema and sibling 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 burden. 'No identifiers are retained' adds some useful data-handling context, but the description says nothing about side effects, whether this is read-only, authentication needs, or what happens with the inputs. This is minimal disclosure for a tool with zero annotation coverage.

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

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

The description is only two sentences long, with no filler or repetition, and it leads with the intended purpose. However, the phrasing 'this request' is vague, which slightly reduces the structural value of the front-loaded sentence.

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 output schema, and no annotations, an agent has very little to work from. The description does not explain what compatibility means, how the parameters combine, what output to expect, or when this tool is appropriate compared to its many siblings.

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 all four parameters already have individual descriptions. The tool description adds no parameter-specific meaning beyond the schema, but the baseline of 3 applies because the schema already documents semantics adequately.

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 the verb 'Show' and mentions classification, but it never identifies what is being classified: 'this request' is ambiguous and no resource is named. It also does not distinguish the tool from siblings such as compat-sse, normalize-url, or validate-json.

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 privacy hint 'No identifiers are retained' implies a use case, but the description does not state conditions, exclusions, or relationships to the 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 provided, so the description carries the full burden of disclosing behavior. 'SSE Accept hint' reveals nothing about side effects, output, errors, or how the input may be consumed or discarded.

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 short, but it is under-specified rather than efficiently structured. It provides almost no useful content for the agent, so the brevity is not a virtue.

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 only a three-word description for a four-parameter tool, the agent cannot determine what inputs to supply, what the tool does, or what to expect in return. This is incomplete to the point of being non-functional.

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

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

The schema already provides descriptions for all four parameters, so schema coverage is 100%. The description adds no parameter-level meaning, but the baseline of 3 applies 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 'SSE Accept hint' is a noun phrase with no verb or resource target. It does not state what the tool does, what it returns, or how it differs from siblings like compatibility or status-catalog.

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 or when to prefer a sibling such as normalize-url, validate-json, or timezone. The description provides no context to support tool 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 present, so the description carries the full burden of behavioral disclosure. It only states the split and the absence of WHOIS/ownership data, but does not disclose expected input, output format, network behavior, or how the json and zone parameters are handled.

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. The qualifier 'without WHOIS or ownership data' usefully sets expectations, though the description could be slightly more informative without losing conciseness.

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

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

With no output schema, no annotations, and four optional parameters, one sentence leaves too much unspecified: which parameter represents the hostname, what the output looks like, and what happens when url, json, or zone are provided. The schema clarifies individual parameters but not the overall invocation contract.

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 schema already explains url, host, json, and zone semantics; the description adds little about which parameter to use for splitting a hostname, but it does not need to compensate for missing schema information.

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 operation: 'Split a hostname into labels', and adds a boundary by excluding WHOIS/ownership data. It is not a tautology and conveys the core function, but it does not differentiate among the four input properties or name sibling tools, so it stops short of a top score.

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, and no sibling tools are mentioned. The phrase 'without WHOIS or ownership data' only hints at scope; it does not explain when to pass url vs host or when not to use the tool.

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

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

No annotations are provided, so the description must disclose behavior itself, but it does not. It fails to state whether the tool returns a list, validates an input, requires arguments, or has side effects, and it says nothing about output format. The description is essentially a label, not a behavioral specification.

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, but the brevity comes at the cost of necessary operational detail. It reads more like a caption or label than a tool definition, and it lacks a verb to clarify the action or behavior.

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 that do not obviously map to 'timezone names', the definition is incomplete. An agent cannot confidently determine what arguments to pass, what the tool returns, or how this tool fits with the related clock/time sibling tools.

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

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

Schema description coverage is 100%, so each parameter has at least some individual meaning in the schema. However, the tool description adds no additional semantic value about how 'url', 'host', 'json', and 'zone' relate to each other or to the stated purpose of providing 'IANA timezone names'; the non-zone parameters appear disconnected from that 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 identifies the resource ('common IANA timezone names') and hints at the context ('for clock calls'), but it is a noun phrase with no explicit verb such as 'list', 'return', or 'look up'. It does not clearly differentiate this tool from sibling tools like 'timezone' or 'utc-time' beyond a vague clock/calls hint.

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 such as 'timezone', 'utc-time', or 'validate-json'. No exclusions, prerequisites, or selection criteria are provided, leaving the agent to guess based on the tool name alone.

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

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

With no annotations, the description carries the full burden, but it only discloses that the fetch is 'public' and returns 'group counts only.' It omits request behavior, error handling, and the fact that the schema contains unrelated parameters like json and zone.

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. However, it is terse to the point of omitting essential contextual information, so it is not maximally effective.

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?

No output schema exists, yet the description never defines what 'group counts' means or what the return shape looks like. It also leaves the 4-parameter schema unexplained in the context of robots.txt, making it difficult for an agent to invoke 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 the schema nominally covers all parameters, the descriptions are mismatched: url references 'normalize or cite,' json is 'to validate,' and zone is a timezone parameter—none clearly tied to fetching robots.txt. The tool description does not explain which parameter to use, so the schema fails to provide usable semantics 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 action ('Fetch a public robots.txt') and the result ('return group counts only'). This specific resource and output restriction distinguish it from generic fetch tools, though it does not explicitly compare it to siblings.

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 or when not to use it. The word 'only' hints that full robots.txt content is not returned, but no exclusions or alternative tool names are mentioned.

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 burden of disclosing behavior. It does disclose the main transformation—query and fragment are dropped—but does not state whether the operation is purely local, what happens for invalid or non-HTTPS URLs, or whether the json and zone inputs have any side effects. The disclosure is helpful but 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?

Two short sentences with no filler; the key transformation is front-loaded and the return values are named. Every sentence 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 schema has four optional parameters, no required fields, no output schema, and no annotations, so the description needs to resolve a lot of ambiguity. It does not explain how json and zone fit into a normalize-url tool, whether url is effectively required, or what the output structure looks like beyond three named components. A URL-only description is materially incomplete for this schema.

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 of 3 applies; the schema already documents all four parameters. The prose adds little beyond listing 'origin, host, and path' as return concepts and does not clarify how json or zone relate to URL normalization, but the schema itself compensates for param-level meaning.

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

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

The description states a clear verb and object ('Return origin, host, and path for a URL') and explicitly defines the transformation (query and fragment are dropped), so the core function is identifiable. However, it does not reconcile this URL-focused purpose with the unrelated json and zone parameters in the schema, leaving some ambiguity about the tool's full scope.

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 'Query and fragment are dropped' implicitly tells an agent this tool is for normalized URL components without query/fragment, and the url parameter description adds 'normalize or cite.' There is no explicit when-to-use or when-not-to-use guidance, and no alternative tools are mentioned, so usage guidance is mostly implied rather than stated.

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

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

No annotations are present, so the description carries the full burden of explaining behavior. It only labels the tool as a 'short catalog' and does not state what happens when invoked, what output is returned, or whether the supplied parameters affect the result.

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 and front-loads the core subject in a single sentence. It does not waste words, though it is so terse that it skirts under-specification.

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 that appear unrelated to HTTP status codes, the description is drastically incomplete. An agent has no basis for knowing what the tool does with the inputs or what a successful call looks like.

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 explains each parameter individually. However, the description adds no connection between these parameters and the catalog behavior, leaving the parameter usage confusing.

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 general resource ('catalog of common HTTP status codes'), but it is a noun phrase rather than an explicit verb-plus-resource statement. It does not say whether the tool returns, lists, or looks up codes, and it does not differentiate itself from siblings beyond the subject matter.

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 or how it compares to alternatives. The four optional input parameters (url, host, json, zone) are never mentioned in the description, so an agent cannot determine when or why to provide them.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic purpose and does not mention output format, behavior for invalid timezones, time source, or any other operational details an agent might need.

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 brief for stating the core purpose, though it skips important usage and parameter-selection details.

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

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

The tool has four optional parameters, three of which seem unrelated to timezone lookup, and no output schema or annotations. The description does not explain which parameter to populate, whether zone is effectively required, or what the response looks like, so the context 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?

The schema has 100% parameter description coverage, so the baseline is 3. The description adds minimal meaning by tying the concept to an 'IANA timezone name,' which maps to the zone parameter, but it does not clarify that url, host, and json appear irrelevant to 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, combining a specific verb ('Current time') with a specific resource. It is distinguishable from siblings like utc-time and iana-zones by name, though it does not explicitly call out 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?

There is no explicit guidance on when to use this tool versus alternatives such as utc-time or iana-zones. The intended usage is only implied by the short phrase, and no exclusions or alternative recommendations are provided.

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

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

With no annotations, the description carries the full transparency burden but only states the result. It does not disclose the timestamp format, confirm that parameters are ignored, or mention any behavior beyond 'current 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 maximally concise and front-loaded; every word contributes. It loses points only because it omits minimal details needed for correct invocation, not because of redundancy.

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

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

For a simple-looking tool with four unexplained optional parameters and no output schema, the description is incomplete: it fails to specify the return format, the role of the parameters, or when to prefer sibling tools like 'timezone'.

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

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

Although the schema documents each parameter, the descriptions like 'HTTPS URL to normalize or cite' and 'JSON text to validate' are unrelated to 'Current UTC timestamp'. The tool description adds no clarification, so an agent cannot tell how url, host, json, or zone relate to this tool's purpose.

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

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

The description 'Current UTC timestamp' clearly conveys the output resource and the implied operation of retrieving the current UTC time. It does not use an explicit verb or contrast with the sibling 'timezone', so it stops short of full 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 rather than 'timezone' or 'iana-zones', nor whether the four optional input properties affect the result. The agent receives no context for choosing between utc-time and its 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?

The phrase 'The body is discarded' is a useful behavioral disclosure that tells the agent the check has no persistent side effect. However, with no annotations and no output schema, the description does not say how the validity result is returned or how invalid or empty input is treated.

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, no filler, with the core action front-loaded and the key side effect in the second sentence. The description earns its brevity.

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

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

For a tool with no annotations, no output schema, and a four-parameter schema, this description is too thin: it fails to explain which parameter is the body, whether a call requires any argument, or what the caller receives back. The irrelevant url/host/zone parameters make the gap worse.

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%, three of the four parameters (url, host, zone) describe unrelated concepts such as normalization and IANA timezones, and the description never maps 'body' to the json parameter. The json parameter is clearly described, but the overall schema actively muddies invocation semantics.

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 and resource — 'Check whether a body is valid JSON' — which clearly matches the tool name. It is not a pure tautology, but it does not distinguish validate-json from the similarly named sibling json-validator.

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 such as normalize-json or json-validator, and no mention of prerequisites or exclusions. The only hint is the purpose itself, which is implied rather than stated.

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