solar_correlation

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

No annotations provided, but description discloses grouping by SFI bracket, output metrics, and the physical effect (HF vs. lower bands). Adds useful behavioral context beyond the schema.

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?

Two sentences plus a note, extremely concise with no wasted words. Front-loaded with question and explanation.

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?

Output schema exists, so description doesn't need to detail return structure. Explains grouping and metrics. Could mention data source explicitly, but it is a parameter. Complete enough for a correlation tool.

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 coverage is 100%, so baseline 3 is appropriate. Description does not add new parameter details beyond what schema provides, but gives context on how parameters (band, grids, source) are used in analysis.

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?

Description clearly states the tool's purpose: analyzing how solar flux affects propagation on a specific band, and describes output metrics (spot counts, average SNR, reliability). Distinct from siblings like band_openings or band_summary.

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?

Implied usage context (when to analyze SFI correlation), but no explicit when-not-to-use or comparison with sibling tools. Limited guidance for an agent to differentiate.

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