data_get_pine_lines

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds that pagination is scoped per study, which is real behavioral context, but it leaves unexplained why a read tool carries write-guard parameters (target_id, expected_layout_id) and does not mention what happens when offset exceeds available data.

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?

One short sentence with the resource and the pagination scope front-loaded and no filler. It is efficient but so terse that some of the omission is under-specification rather than true conciseness.

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?

A 5-parameter read tool with no output schema and 40% schema coverage needs more from the description: what a 'line' primitive contains, what entity_id identifies, and the default/max paging behavior. As written, an agent cannot confidently construct a call without guessing at entity_id.

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 only 40%: limit, offset, and entity_id have no descriptions at all. The description's 'per-study pagination' hints that limit/offset operate within a study, but entity_id — the key selector — is never explained in either place, so the gap is not compensated.

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?

Specific verb ('Read') plus a specific resource ('Pine-generated line primitives') and a scope qualifier ('per-study pagination'). The sibling set (data_get_pine_labels, data_get_pine_tables, data_get_pine_boxes) makes the resource distinction inferable, though the description 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?

There is no guidance on when to call this versus the other data_get_pine_* readers, and no stated prerequisites (e.g., a chart/study must be loaded). Only the pagination scope is mentioned, which is behavioral, not usage-selecting.

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