data_get_pine_lines

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

With no annotations, the description carries the full burden and does well: it declares 'SIDE EFFECTS: None (Read-only)' and a concrete limitation ('Only reads lines drawn by active Pine studies'). It also discloses post-processing behavior (deduplicated, sorted, per study). Minor gap: no statement on empty/missing-study behavior.

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?

Front-loaded with the core purpose, then tightly organized WHEN TO USE / SIDE EFFECTS / LIMITATIONS blocks. Every sentence earns its place with no filler.

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 output schema, the description usefully sketches the return shape ('deduplicated, sorted price levels per study'). Combined with full schema coverage of both params and the read-only declaration, an agent has almost everything needed, though the verbose-mode return shape stays undocumented in prose.

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 both parameters are already fully documented in the schema; baseline 3 applies. The description reinforces study_filter's purpose ('target specific scripts') but adds no syntax or format detail beyond what the schema provides.

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 and resource ('Read horizontal price levels drawn programmatically by Pine Script indicators') and pins down the exact mechanism (line.new). It is clearly distinguishable from the sibling draw-type readers data_get_pine_labels, data_get_pine_tables, and data_get_pine_boxes.

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 WHEN TO USE block gives a concrete trigger ('indicator draws support/resistance or session levels via line.new') and points at study_filter for targeting scripts. It stops short of naming explicit alternatives or exclusion conditions, so it is clear but not fully routing.

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