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

With no annotations at all, the description carries the full behavioral burden yet says nothing about mutation, permissions, output format, or severity behavior. A lint tool's behavioral profile is entirely undisclosed.

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 short and front-loaded, but the content is a duplicated title rather than compressing any useful information; conciseness here reflects under-specification rather than efficiency.

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 three-parameter tool with no annotations and no output schema, the description offers no information whatsoever about inputs, behavior, or results. It is completely inadequate to guide correct invocation.

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_description_coverage is nominally 100%, the schema texts are tautologies ('Text to process', 'Input to process', 'Dockerfile to process') that provide no real meaning, and the description adds nothing to disambiguate which of the three near-duplicate parameters to supply. The effective coverage is far below the nominal figure, so the description should compensate and does not.

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 'Dockerfile Lint: Dockerfile Lint' merely restates the tool name and title with no added verb, scope, or distinguishing detail. An agent can guess it lints Dockerfiles, but nothing states what it checks or returns.

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?

No indication of when to use this tool versus alternatives, no prerequisites, no mention of input expectations. Zero guidance is provided.

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