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

With no annotations, the description carries the burden and does well: it discloses the return shape (findings with line, why, fix, and a score) and the payment mechanic ($0.005 USDC per call via x402 on Base), which is real operational context an agent needs before invoking. It stops short of stating failure modes or whether the call is idempotent/read-only, but lint semantics make that largely self-evident.

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?

One dense, front-loaded sentence listing the checks, followed by a short returns/pricing note. The rule enumeration is long but each item is a concrete check, so it earns its space; the pricing clause is separable metadata rather than description content.

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 single-input lint tool with no output schema and no annotations, the description supplies what is missing: the checks performed, the structure of findings, the score, the input size limit (in schema) and the cost model. Nothing an agent needs in order to call it correctly is absent.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents 'content' as the full file text with a 100 KB cap. The description adds nothing about the parameter, which is acceptable at this coverage level but unremarkable.

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?

Names a specific verb (lint) and resource (Dockerfile) and enumerates the exact rule families checked, so the agent can tell it apart from ciaudit_compose and ciaudit_github_actions at a glance.

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?

Usage is only implied by the resource name 'Dockerfile'; there is no explicit statement of when to prefer this over ciaudit_compose or what input qualifies beyond the schema's 100 KB note. An agent can infer the context, but nothing routes it deliberately.

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