data_get_pine_labels

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

With no annotations provided, the description carries the full burden and does reasonably well: it explicitly states 'SIDE EFFECTS: None (Read-only)' and a meaningful limitation that only labels currently in chart memory are readable. It does not describe return structure in detail, but the safety and scope profile is clearly disclosed.

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 purpose sentence followed by labeled WHEN TO USE, SIDE EFFECTS, and LIMITATIONS sections. Every sentence earns its place with zero 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?

No output schema exists, but the verbose parameter's description indicates the return shape (raw label data with IDs/colors/positions vs text+price only), so return expectations are covered indirectly. The definition is complete enough for an agent to invoke correctly, with only minor gaps in return-format detail.

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 schema already documents verbose, max_labels, and study_filter with defaults and semantics. The description adds no parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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 (read) and resource (text annotations/labels drawn by Pine Script indicators via label.new) paired with price coordinates. This clearly distinguishes it from siblings like data_get_pine_lines, 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 clause gives concrete trigger conditions (indicator displays bias markers, order block tags, or targets via label.new). However, it does not name alternative tools or state when to prefer a different data_get_pine_* sibling over this one.

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