Analyze Ramps

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

Beyond the readOnly and idempotent annotations, the description discloses meaningful behaviors: it supports hourly and five-minute cadence where available, skips non-consecutive observations, reports MW per interval and MW/hour, and never fills missing values. This gives an agent a clear model of how the tool processes data.

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 two dense sentences with no filler. The primary action is front-loaded, and each clause adds a distinct behavioral fact without repetition.

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?

Given the rich input schema, annotations, and the presence of an output schema, the description covers the essential behavioral gaps: cadence handling, missing-value policy, non-consecutive observation handling, and output units. Nothing critical for invoking the tool correctly appears to be missing.

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 100%, so the baseline is 3 even though the description does not add much per-parameter detail. The high-level mention of series types and cadence aligns with the schema but does not deepen understanding beyond what the parameter descriptions already provide.

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 analysis ('Calculates cadence-aware up/down ramps') and enumerates the applicable resources: AIL, net load, wind, solar, or asset CSD generation. This clearly distinguishes it from sibling analysis tools like analyze_net_load or analyze_generation_mix.

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 description implies usage through its capability statement, but it does not explicitly say when to choose this tool over alternatives or when not to use it. It provides some context about cadence support and data handling, but no exclusionary guidance relative to sibling tools.

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