pvsyst_get_component

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

With no annotations, the description carries the burden itself and does a substantial job: it discloses paging, returned data categories, curve CSV behavior, error reporting for omissions, and several important caveats about unverified coefficients, per-MPPT limits, and IDCMax=0. It does not discuss permissions or side effects, but the read-oriented framing and data caveats are unusually detailed.

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 dense, jargon-heavy block with eight sentence-like clauses and poor front-loading. Some details are useful, but the lack of structure makes it hard to scan and the opening does not orient the agent before diving into specialized return semantics.

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?

There is no output schema and no annotations, and while the description explains many return-side caveats, it omits essential caller information such as accepted component_type values, filename conventions, and why to use this tool rather than list_components or validate_component. The result is incomplete for a six-parameter tool with 0% schema coverage.

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% for six parameters, so the description needs to compensate, but it only explains include_curve_csv and vaguely implies paging. It never clarifies component_type allowed values, filename expectations, library semantics, or offset/limit behavior.

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 makes clear that this tool reads component-file internals, including text, allowlists, SHA, curve paths, field units, and remarks. The verb-and-resource combination is specific enough to separate it from a generic list or simulation tool, though it does not explicitly contrast itself with siblings like pvsyst_list_components, pvsyst_validate_component, or pvsyst_compare_components.

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 gives caveats such as 'static inspection does not verify simulation behavior' and 'CSV export does not expand edit support,' but these are limitations rather than when-to-use guidance. It never says when an agent should choose this over list_components, validate_component, compare_components, or project_components.

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