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

The description adds material context beyond the annotations: the operation is paid (0.01 USDC via x402 / X-Bazaar-Key), which the readOnlyHint=false / idempotentHint=true / openWorldHint=true annotations do not convey at all. It does not describe failure modes or what a lint result contains, but the payment/auth disclosure is a genuinely useful addition.

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?

A single sentence with the payment/auth banner front-loaded and the verb-resource-target sequence following. Every clause carries information; nothing is redundant.

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?

There is no output schema and no annotation coverage of return behavior, yet the description never indicates what the linter produces (findings, severity, pass/fail, x402-readiness verdict). For a diagnostic tool whose entire value is its output, that is a meaningful gap, though the scope and payment terms are otherwise complete.

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 coverage is 100%, so the baseline is 3, but the description actually adds meaning: it implies inputs beyond operation_id (HTTP method, path, HTTP 402 response definition), which is consistent with additionalProperties=true and tells the caller these are expected payload fields. It stops short of explaining formats for those fields.

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?

States a specific verb ('Lint') and resource ('an OpenAPI operation'), and enumerates the inspected dimensions (operation_id, HTTP method, path, 402 response) plus the target outcome ('AI agent tool-calling and x402 readiness'). It is distinguishable from generic siblings like json_schema_lint or mcp_manifest_lint, though it never names those alternatives explicitly.

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?

The phrase 'for AI agent tool-calling and x402 readiness' implies the context in which to use it, but there is no explicit when-to-use/when-not guidance and no routing against the many other *lint siblings (agent_card_lint, mcp_manifest_lint, json_schema_lint). An agent must infer selection from the resource name alone.

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