pine_get_console

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

No annotations are provided, so the description must carry the behavioral burden. It does disclose side effects ('None (Read-only)') and a practical limitation ('Console output must be enabled in the script'), though it does not cover return shape or authorization context.

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 front-loaded with purpose, then succinctly labels WHEN TO USE, SIDE EFFECTS, and LIMITATIONS. Every sentence earns its place with no redundancy.

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 zero-parameter, read-only console log tool with no output schema and no annotations, the description provides all essential details: what it reads, when to use it, safety, and a precondition. Nothing critical is missing.

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 tool takes zero parameters, so there is nothing for the description to add beyond the schema. Baseline for zero-parameter tools is 4.

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 uses a precise verb ('Read') and names the specific resource ('runtime logs and compiler messages from the Pine Editor console window'), including concrete examples of log functions. It clearly distinguishes this from compile-error retrieval tools by focusing on console output.

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?

It provides an explicit WHEN TO USE section: debugging Pine Script runtime behavior or inspecting custom log outputs. It gives clear context but does not name alternative tools (e.g., pine_get_errors) or state when-not to use it.

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