Export ProjectionLab Data

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

The description adds context beyond the readOnlyHint annotation by disclosing that the tool returns a script rather than performing the export directly, and that it reads the API key from sessionStorage set during pl_setup. This is useful behavioral information. It does not contradict the annotation, and while it doesn't detail return format, the added context is valuable.

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 three sentences, front-loaded with the core purpose, and every sentence adds necessary operational detail. There is no repetition of schema or annotation information, and no filler content.

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?

Given the zero-parameter input, the readOnlyHint annotation, and lack of output schema, the description adequately covers how to use the tool and its prerequisites. It explains the returned script's execution context and dependency on setup. It could mention the data format or error scenarios, but these are not essential for invocation.

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 has zero parameters, and the description correctly avoids discussing any. The parameter schema is empty, and the description doesn't need to compensate. Baseline for 0 params is 4, which is appropriate here.

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 opens with a specific verb and resource: 'Returns a JavaScript string that exports all ProjectionLab data via the Plugin API.' This clearly distinguishes it from sibling tools like pl_setup, pl_snapshot, pl_list_snapshots, and pl_restore, which handle setup and snapshot lifecycle. The purpose is unambiguous and informative.

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 description provides clear execution context: 'Execute this script in the browser using the Playwright or chrome devtools MCP.' It also states the prerequisite that pl_setup must have run and that rerunning is necessary if the tab was closed. This is practical guidance, though it does not explicitly mention alternatives or when not to use the tool.

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