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

With no annotations, the description carries the full burden. 'Input discarded' is the only behavioral claim and does suggest a side-effect-free read, but it is undefined jargon that does not explain what is computed, what is returned, or why nine unrelated inputs are accepted and ignored.

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?

It is very short, but the brevity comes at the cost of meaning: two cryptic fragments rather than a front-loaded statement of purpose. Nothing is padded, yet nothing useful is conveyed.

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 nine free-form parameters, no annotations, and no output schema, the description omits essentially everything an agent needs: what the call does, what it returns, and how the nine ignored inputs relate to a 'charset' check. It is completely inadequate for this surface area.

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 itself documents all nine parameters, and the baseline is 3 even with no parameter detail in the description. The description adds nothing about syntax or which parameters matter, but it is not required to given the coverage.

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 'Xxencode charset, input discarded' is a near-tautological restatement of the name (xx-len) plus a cryptic fragment; it never states a clear verb+resource or what the tool actually computes. An agent cannot determine from this text whether it encodes, measures length, or validates anything.

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 when-to-use guidance, no exclusions, and no mention of the many obvious siblings (search-query-len, memory-key-count, file-path-ok, validate-json) that overlap with several of this tool's parameters. The 'input discarded' fragment hints the call is side-effect-free but gives no routing context.

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