reset_firegex

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

The description discloses the destructive nature of delete=True and the safe behavior of delete=False. It does not mention potential side effects like network interruption or authentication requirements, but the warning about danger is strong. With no annotations, the description carries the full burden and does well.

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: first states the main action, second provides critical warning and usage advice. No wasted words, front-loaded with essential information.

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 tool's simplicity (one parameter, no nested objects), the description covers the essential behaviors. An output schema exists so return values need not be explained. It could mention prerequisites or invariants (e.g., 'requires admin privileges'), but it is largely complete.

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 schema has 0% description coverage, but the description fully explains the 'delete' parameter: it contrasts the two behaviors and warns about danger. This adds significant meaning beyond the boolean type in the schema.

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 resets Firegex's nftables state, and distinguishes between two modes (delete=True vs delete=False). It has a specific verb and resource, and among siblings there is no other reset tool, making it distinct.

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?

Explicit guidance is given on when to use delete=True (dangerous, wipes databases) vs delete=False (safe flush and reload). This helps the agent choose the appropriate behavior without needing to consult other tools.

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