EBCDIC to ASCII

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

With no annotations, the description carries the full burden. It usefully discloses the output representation ('returned as hex digits') and the default codepage, but says nothing about hex formatting (case, separators), or what happens when a character cannot be represented in the target codepage.

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, zero filler, and the most decision-relevant fact (hex output) is front-loaded alongside the direction. 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 two-parameter converter with no annotations and no output schema, the description covers direction, output representation and codepage options. It stops short of completing the picture on output shape and failure modes, which an agent would still have to discover by calling it.

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 50%, and the one undescribed parameter (codepage) is fully compensated for: the description enumerates cp037, cp500 and cp273 and confirms cp037 as the default, matching the schema. It does not explain how the pages differ or what an invalid value does, which keeps it below a 5.

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 ('Encodes ASCII text to EBCDIC bytes') and adds the return format. Direction is unambiguous, which implicitly separates it from the inverse sibling ebcdic_to_ascii, though that sibling is never named.

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?

Usage is only implied by the encode direction and the codepage list; there is no explicit statement of when to use this versus ebcdic_to_ascii or when a non-default codepage is appropriate. Adequate for a simple one-way converter, but nothing routes the agent explicitly.

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. It confirms the operation is a pure decode to text but says nothing about behavior on malformed/odd-length hex, invalid byte sequences, or what happens for a codepage mismatch — the things an agent most needs to know before relying on it.

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 first sentence is tight and front-loaded with the essential transformation. The second sentence is a self-deprecating aside that consumes roughly half the text without conveying any operational information.

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 two-parameter pure function with no output schema, the description covers input encoding, output type, and supported code pages, which is close to sufficient. It falls short on edge-case behavior (invalid hex, decoding failures), which matters more here because no annotations exist to cover it.

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 50%: 'hex' is documented in the schema and the codepage enum/default are structurally visible but undescribed. The description restates the code page options (cp037 default, cp500, cp273), which fills that gap at the surface level but adds no semantic meaning about when to choose a given code page.

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 first sentence gives a specific verb (decodes), a specific input form (EBCDIC bytes as hex digits), and a specific output (text), so the transformation is unambiguous. It does not explicitly position itself against the sibling ascii_to_ebcdic (the inverse direction), but the direction is clear enough that an agent can infer it.

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 statement of when to use this versus ascii_to_ebcdic, nor of prerequisites or error conditions. The second sentence ('Nobody needs this; it exists so that a call to it means something') is meta-commentary that muddies rather than guides, leaving the agent to infer usage purely from the verb.

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 exist, so the description carries the full burden, and it does disclose a non-obvious side effect the agent would otherwise miss: 'this server records who connects.' It also states the return behaviour (the text is echoed back), though it doesn't describe the response shape or whether the recording is logged/persisted.

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 waste, leading with what the tool does before the diagnostic rationale. 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 trivial one-parameter echo with no output schema, the description covers the input, the return behaviour, and the side effect. Only the exact response format/any recording details are absent, which is minor for a tool this simple.

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 single parameter has 100% schema description coverage ('Text to echo back'), and the description's 'text you send' adds nothing beyond that. Baseline 3 is appropriate since the schema fully documents the 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?

States a specific verb and resource ('Returns the text you send') plus a secondary diagnostic purpose, which is unambiguous for a one-parameter tool. It doesn't explicitly distinguish itself from the ascii/ebcdic siblings, but the resource difference is obvious enough that an agent won't confuse them.

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 usage as a connectivity/behaviour probe ('Exists to measure MCP client behaviour'), which is helpful context for why one would call it. However, it never says when to prefer it over the sibling encoding tools or what condition makes it appropriate, leaving selection guidance implicit.

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