pvsyst_read_batch_results

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

With no annotations, the description carries the full behavioral burden. It implies a read of a CSV file but does not say whether it is read-only, what happens if summary_name is missing or invalid, how columns affect output, or what shape the returned values take.

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 front-loaded sentence with a useful [Results] tag and no filler. It is concise, though brevity comes at the cost of missing guidance.

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?

For a tool with two parameters, zero schema descriptions, no annotations, and no output schema, the description is too thin. An agent cannot confidently construct a correct call or interpret the returned values from this text alone.

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. It only indirectly references summary_name (the '*Results.CSV summary') and never explains the columns parameter or its default of E_Grid,PR.

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?

States a specific verb (read) and resource (SIM_* scenario values in a UserBatch/*Results.CSV summary), which is more than a tautology. However, it relies on PVsyst-specific jargon and does not distinguish itself from sibling readers like pvsyst_read_results or pvsyst_read_rows.

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?

Gives no indication of when this batch-summary reader should be used instead of pvsyst_read_results or pvsyst_read_rows. No prerequisites, alternatives, or exclusion criteria are stated.

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