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

With no annotations provided, the description carries the full disclosure burden. It only says 'bytes discarded', which is vague and unexplained: which bytes, when, and with what effect? It does not state return behavior, side effects, failure modes, or whether any input is actually examined.

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 short, but it is an under-specified fragment rather than a concise explanation. It has no verb, no sentence structure, and omits essential information. This is over-compression, not 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?

Given 9 optional parameters, no output schema, no annotations, and a large sibling group, the description is radically incomplete. The agent has no way to know what to pass, what the tool returns, what a successful call looks like, or why it should be selected over the many similar 'shape' and 'ok' 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?

Although schema coverage is 100%, the parameter descriptions describe unrelated contents: Git refs, URLs, city names, timezones, etc. None of them clearly carries the bytes that would be examined for a UTF-32LE BOM. The tool description adds no mapping between parameters and its supposed purpose, so the high schema coverage does not compensate.

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 is a noun fragment: 'UTF-32LE BOM presence, bytes discarded.' It names the apparent resource but never states an action such as 'checks', 'returns', or 'validates'. This mostly restates the tool name 'utf32le-ok' without giving the agent a concrete operation to invoke.

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 input to supply, or how it differs from sibling tools like 'file-path-ok' or 'domain-shape'. The 9 optional schema fields are all described but none are connected to a BOM check, so an agent cannot infer a correct invocation context.

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