plc_open_project

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

Annotations declare non-read-only, non-idempotent, non-destructive, closed-world behavior, and "immutable local storage" adds a useful detail: the tool materializes a snapshot rather than working in place, which is consistent with the write-flagged annotations. However, it says nothing about where that storage lives, what happens if the path was already opened, whether re-invocation creates duplicates, or any permission requirements. Given the annotation set already covers the safety profile, the description contributes some but not much behavioral 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?

Two short sentences with the action front-loaded and the return values summarized at the end; no filler. It is tight, though the brevity comes at the cost of the missing details noted elsewhere.

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?

An output schema exists, so return values need not be re-explained, but for a tool that creates immutable local storage from a single opaque path argument the description should say what that storage is and how it relates to the path. With no annotations covering destination or repeat-invocation behavior, the definition is too thin to call the tool correctly without trial and error.

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?

There is a single required parameter, "path", with 0% schema description coverage, so the description carries the entire burden of explaining it. It never states whether the path is a local .smc2 file, a project directory, or something else, nor any format constraints. The gap is left entirely to inference.

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?

"Acquire a native SMC2 into immutable local storage" gives a verb and a resource, but "SMC2" is unexplained jargon and the phrasing never clarifies whether this opens a file, copies it, or imports it in-place. It also fails to separate itself from nearby siblings such as plc_ide_open_existing, plc_ide_open_copy, or plc_get_project_info. The closing clause about returning project ID, revision, and coverage helps, but the core action stays ambiguous.

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 statement of when to use this tool, no prerequisites, and no reference to any alternative. With siblings like plc_ide_open_existing and plc_ide_open_copy in the catalog, the agent is left to guess which entry point applies to a given scenario.

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