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

No annotations are provided, and the description fails to disclose any behavior: whether it lints a file or string, what kinds of issues it reports, whether it requires network access, or what the output format looks like. The description carries the full burden and does nothing to meet it.

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 rather than concise writing. It contains a single repetitive phrase that spends its only words restating the name without earning its place.

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 no annotations, no output schema, and a description that repeats the tool name, the definition is wholly inadequate. Among a massive set of markdown and lint-related siblings, an agent cannot determine what input to provide, what output to expect, or even what 'lint' means here.

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 baseline of 3 applies even though the description adds nothing about the 'input' parameter. The schema's own description ('Input to process') is generic and unhelpful, but the parameter is at least structurally documented.

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 'Markdown Lint: Markdown Lint' is a pure tautology—it merely restates the tool name and title without any verb, resource, or explanation of function. It provides no information distinguishing it from the many markdown-related sibling 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 no guidance about when to use this tool, what inputs are appropriate, or how it differs from alternatives like x402-markdown-links, x402-markdown-table, or x402-markdown-toc. The description offers zero contextual or routing information.

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