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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It discloses only that bytes in the KOI8-U high-bit band are discarded, and says nothing about side effects, return values, edge cases, or which inputs are affected.

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 effective conciseness. The phrase is cryptic and lacks the structural cues an agent needs to interpret a 10-parameter 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?

With 10 parameters, no annotations, and no output schema, the description should explain return behavior, invocation intent, and parameter relevance. 'KOI8-U high-bit band, bytes discarded' leaves essential context missing, so the definition is not complete enough for reliable agent use.

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

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

Schema description coverage is 100%, so the schema already documents all 10 optional parameters in detail. The description adds no parameter-specific meaning, so the baseline of 3 applies; it does not compensate further.

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 phrase 'KOI8-U high-bit band, bytes discarded' names a subject and an effect, but does not state a clear verb or the actual operation, such as validating, checking, or transforming input. With 10 unrelated-looking parameters and no output schema, an agent cannot confidently determine what this tool does or when to call 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 guidance about when to use this tool, what conditions warrant it, or how it differs from sibling tools such as normalize-url, validate-json, or file-path-ok. The description implies a narrow encoding-related behavior but gives the agent no practical selection criteria.

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