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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, non-mutating analysis call. The description adds the analysis scope (which classes of defects are detected), which is useful, but says nothing about what is emitted (errors vs warnings), severity levels, or whether linting can be partial.

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 front-loaded sentence with the verb and resource first, followed by a dense but informative list of checks. No filler sentences, though the trailing list is long enough to border on inventory-dumping.

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 read-only analyzer with no output schema, the description should convey what the caller receives (diagnostics, warnings, error list). It describes what is checked but not what comes back, which is the main remaining gap.

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 with 100% schema description coverage ('Pine Script source'), so the schema fully carries the parameter burden. The description adds no syntax or format guidance beyond the schema, which is the expected baseline at this coverage level.

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 (TradingView Pine Script) and enumerates the concrete check categories it performs, so an agent knows exactly what analysis it runs. Sibling differentiation is weakened by 'plus all integrity checks', which overlaps with the pine_integrity sibling rather than drawing a boundary against it.

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 enumerated checks imply the use case (validate Pine source before running it), and 'plus all integrity checks' hints that this tool is a superset of pine_integrity. However, it never explicitly says when to pick this over pine_integrity or what input conditions are required, leaving routing to inference.

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