Ultrabrain Reset

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

Annotations already mark the tool as destructive and non-read-only. The description adds the key behavioral detail that resetting can affect one or all sessions based on the boolean flag, which goes beyond the annotations.

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, dense sentence that conveys the core action and parameter implication without any wasted words. It is front-loaded with the verb and resource.

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 moderate complexity, lack of output schema, and annotations covering destructiveness, the description is largely complete. It could mention side effects (e.g., loss of session state) but is sufficient for an agent to understand the tool's purpose.

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 50% (session_id described, all_sessions not). The description directly adds meaning to 'all_sessions' by explaining its effect. For session_id, the schema already provides default and optionality, so no further value is added.

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 uses the specific verb 'reset' and resource 'Ultrabrain session', clearly distinguishing it from siblings like 'start' or 'think' which serve different purposes. The scope (one or all sessions) is explicitly stated.

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?

The description implies use when resetting sessions but provides no explicit guidance on when to use vs alternatives (e.g., 'ultrabrain_start' or 'ultrabrain_update'). No when-not-to-use or exclusion criteria are given.

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