reset_bot

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

No annotations are provided, so the description carries full burden. It discloses destructive behavior (reset logs, sessions, flag users) and the authentication requirement. This is transparent for a reset operation, though it does not detail reversibility or side effects on other bot components.

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?

Extremely concise with two sentences. The first sentence front-loads the action, the second provides the requirement. No superfluous words or repetition.

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 destructive reset tool with no output schema, the description covers the core action and authentication. However, it omits details about the impact on other bot data (e.g., commands, broadcasts) or the exact behavior of flagging users, leaving some contextual gaps.

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 description coverage is 100% for the single parameter (botid). The description does not add any additional information beyond what the schema already provides, so it meets the baseline without enhancement.

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?

Clearly states the tool resets bot logs, sessions, and flags users as just-created. This is a specific verb+resource action that distinguishes it from siblings like clear_bot_storage or delete_bots.

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?

Provides the authentication requirement (sk_* key) but lacks guidance on when to use this reset vs alternative tools like clear_bot_storage or delete_bots. The description implies usage but does not explicitly state context or exclusions.

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