alert_gas

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

No annotations are present, so the description must disclose behavioral implications. It only says 'Create an alert' without explaining that this is a persistent side-effecting operation, how to manage the alert afterward, or any prerequisites or limits. The lack of behavioral information is a significant gap for a creation 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?

The description is a single, front-loaded sentence with no wasted words. It earns its place by clearly naming the action and subject.

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?

The tool has no output schema and no annotations, and the description does not cover expected return values or subsequent management options (alert_list, alert_pause, etc.). For a side-effecting creation tool in a rich alert ecosystem, this level of information is insufficient.

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 the baseline is 3. The description and schema explain that chain, condition, and targetGwei are used for gas price conditions, but neither adds deeper meaning such as how condition and targetGwei interact (e.g., alert when gas price below target). The description contributes minimal value beyond the structured parameters.

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 function - creating an alert for gas price conditions - using a specific verb and resource. It differentiates from sibling alert tools by specifying 'gas price', unlike alert_price, alert_whale_movement, etc., though it omits details on how conditions are defined.

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?

No guidance is provided on when to use this tool versus other alert creation tools or how it fits into the alert management lifecycle. The description offers no context for selecting this tool over alternatives like alert_price or alert_contract_event.

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