reactor_timing

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

Discloses read-only nature and that no wallet is needed, which is valuable since no annotations exist. Lists outputs but does not mention freshness or rate limits; adequate for a prediction tool.

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, no filler, front-loaded with main action and outputs. Highly efficient.

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 no output schema, description provides a high-level summary of return values but lacks specifics on format (e.g., list vs. single value). Adequate for a simple 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?

No parameters in schema, so description carries full burden. It explains what the tool returns beyond the empty schema, including multiple signals. Baseline 4 applies.

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 the tool's purpose: predicting reactor fire timing, with specific outputs (time, clustering, prime imminent, buy-window signal), differentiating it from siblings like 'fire_reactor' and 'get_reactor_list'.

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?

Usage is implied through context, but no explicit guidance on when to use this vs. other timing/analysis tools; no alternatives or exclusions mentioned.

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