pvsyst_project_handoff

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

With no annotations, the description carries the full burden and does well: it explicitly states readonly behavior, excludes GUI, license query, simulation, repairs, and writes, and clarifies that ready/needs_review only describe the handoff while native_consumption_verified remains false. It still does not describe failure behavior or rate limits, so it is strong but not exhaustive.

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 compact, front-loads the read scope, and avoids filler. It is dense and somewhat run-on, especially the parenthetical engineering clauses, but every sentence contributes meaning.

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?

The description conveys the conceptual handoff contents and readonly constraints, which is useful given no output schema. However, it does not fill the parameter documentation gap or explain the response shape, and it lacks explicit routing against similar project/variant inspection tools, leaving material gaps for correct 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?

Schema description coverage is 0%, so the description must compensate for all three parameters. It only gestures at the declarations parameter via 'explicit caller declarations' and provides no meaning, format, or expected values for project, variant, or declarations. This leaves the agent largely dependent on naming alone.

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 names a specific read operation and enumerates the saved engineering data it returns: equipment, counts, orientation/circuit relationships, input dependencies, declarations, inherited values, missing inputs, and review items. It is clear what the tool does, but it does not explicitly distinguish it from nearby siblings such as pvsyst_review_project_inputs or pvsyst_inspect_project.

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?

Usage is implied by the engineering handoff framing and the readonly constraints, but there is no explicit statement of when to use this tool instead of pvsyst_review_project_inputs, pvsyst_inspect_project, or pvsyst_get_variant_parameters. The agent must infer the intended handoff scenario.

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