List Sunsynk plants

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

The annotations already establish this as a read-only, open-world call, and the description adds meaningful output context: id, name, current PV power, generation values, and status. It does not mention pagination or latency, but for a zero-parameter listing tool the behavioral disclosure is sufficient.

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?

A single sentence front-loads the action and resource, then compactly lists the returned fields and units. Every phrase earns its place and nothing is redundant.

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 tool has no input parameters, and the description names all relevant output fields since no output schema exists. Combined with the read-only/open-world annotations, this gives an agent everything needed to understand and invoke the tool correctly.

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?

With zero parameters)Skip, the input schema carries no semantic burden and the baseline is 4. The description adds no parameter detail because none exists.

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 specific verb ('List') and an explicit resource ('solar plants (sites) on the Sunsynk Connect account'). It enumerates the exact returned fields, distinguishing it from sibling tools like sunsynk_list_inverters and sunsynk_live_status.

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 account-scoped phrasing and explicit focus on plants/sites make the tool's intended use clear. It does not name sibling alternatives or state when not to use it, but the listing intent is unambiguous and no prerequisites are implied.

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