get_solar_flares

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

No annotations are present, so the description must fully disclose behavior. It reveals that the tool fetches recent flare event data with begin/peak/end times and peak class. However, it omits details on data freshness, rate limits, or whether the operation is read-only (though that is implied). The output description is partially covered by the existing output 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?

The description is two sentences plus a usage tag, front-loading the core purpose. Every sentence adds value with no redundancy or fluff.

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 simple tool with one parameter and an output schema, the description adequately covers purpose, parameter, output format, and usage context. It could mention potential limitations (e.g., maximum days, data source) but is sufficient for effective agent selection.

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?

The only parameter 'days' is explained in the description as 'last `days`', clearly indicating it controls the lookback window. Since the input schema has no description and only declares type and default, this addition is meaningful and compensates for the 0% schema coverage.

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 clearly states it returns 'Recent GOES X-ray solar flares' with specific classes (C/M/X), and explicitly distinguishes itself by noting it's best for current flare activity queries. This verb+resource combination effectively sets it apart from sibling tools like get_aurora_forecast or get_kp_index.

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 provides explicit usage guidance: 'Best for "biggest recent flare?" / current flare activity.' This indicates when the tool is appropriate, though it does not explicitly list exclusions or alternatives. The sibling tools are distinct enough that no further disclaimers are necessary.

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