pine_new

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

No annotations are present, so the description must carry full responsibility for disclosing side effects. It only states 'Create a new blank Pine Script' without explaining whether this replaces the current editor content, opens a new tab, or returns some identifier. This lack of detail is a significant gap for a creation tool.

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?

The description is a one-sentence, front-loaded statement with no unnecessary words. It efficiently communicates the core purpose and is highly concise.

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?

This is a simple create operation, but the description is too sparse to be considered complete without annotations or an output schema. It fails to mention critical details such as the effect on the current script, return value, or any prerequisites, leaving the agent with incomplete information about how to use the tool correctly.

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?

The single required parameter 'type' has full schema coverage (100%) with a clear description and enum values. The description does not add extra parameter semantics, but the schema already provides adequate detail, so the baseline score of 3 applies.

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?

The description explicitly states 'Create a new blank Pine Script', which uses a specific verb and resource to clearly convey the tool's function. It is easily distinguished from sibling tools like pine_open (which opens existing scripts) and pine_compile (which compiles), so there is no ambiguity.

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?

No usage context is provided. The description does not mention when to use this tool versus alternatives like pine_open or pine_set_source, nor does it specify prerequisites or typical workflow steps. The agent is left to infer this from the sibling list.

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