erase_blackbox_logs

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

Discloses irreversibility and duration (up to 30 seconds). Since no annotations are provided, the description carries the full burden and provides key behavioral traits beyond the tool's name.

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 concise sentences with front-loaded purpose and critical behavioral notes. No wasted words.

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 parameterless, destructive tool, the description covers purpose, irreversibility, timing, and ordering. Minor improvement could add confirmation or undo information, but it is adequate.

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 input schema has zero parameters, so schema coverage is 100%. The description need not add parameter details; baseline 4 is appropriate.

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 verb 'erase', the resource 'blackbox logs', and the location 'onboard flash memory'. It uniquely identifies the tool's action among many sibling tools that are get/set operations.

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?

Includes a specific usage note: 'call this before any CLI tools in the same session', which provides actionable context. Does not explicitly state when not to use, but the note is clear and directional.

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