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. The phrase 'bytes discarded' hints at some discarding behavior but does not explain side effects, permissions, limits, or what results are returned. The description is far too sparse to inform an agent about the operational behavior of the tool.

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 this is under-specification, not conciseness. It provides almost no useful content, and the few words used ('presence', 'bytes discarded') are ambiguous. A concise description should pack meaning into few words; this does not.

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 output schema, and no annotations, the description is grossly inadequate. An agent cannot determine what inputs are relevant, what the output looks like, how the tool handles destructive or read-only operations, or why it exists. This is far below the minimum viable definition for a tool of this complexity.

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?

While the schema has 100% coverage (every parameter has a description), the parameters themselves appear unrelated to the tool's stated purpose (e.g., 'city', 'feed', 'host'). The tool description does not explain how these parameters are used or why they are needed for a UTF-32LE BOM check. The schema descriptions are generic and do not tie into the tool's function, so the description adds little value beyond the schema.

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 'UTF-32LE BOM presence, bytes discarded' is a fragment, not a clear statement of action. It does not name a verb like 'check' or 'validate', nor does it specify what resource is being acted upon. It is somewhat interpretable as checking BOM presence but is too vague to distinguish from a generic encoding check, and it does not differentiate from sibling shape-check tools.

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 zero guidance on when to use this tool versus any of the 30 siblings (e.g., domain-shape, file-path-ok, jira-key-shape). The description gives no context about typical use cases or conditions that would make this tool preferable. An agent would have to guess based solely on the name.

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