Ultrabrain Reset

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds marginal behavioral context by explaining that setting all_sessions=true resets all sessions, which is more destructive than resetting one. However, it does not detail what 'reset' entails (e.g., data loss, session history clearing).

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 that conveys the core functionality without any wasted words. Every part of the description is essential and immediately understandable.

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 (2 parameters, no output schema) and annotations covering safety, the description is nearly complete. However, it does not explain what 'reset' means operationally (e.g., clearing reasoning state), which would provide fuller context for non-obvious implications.

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 description adds meaning to the all_sessions parameter, which lacks a schema description, by stating it triggers a reset of all sessions when true. For session_id, the schema already provides a description, so the description reinforces it. This compensates for the 50% schema coverage.

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 an Ultrabrain session, with the ability to reset all sessions via the all_sessions parameter. It uses a specific verb-resource pairing ('Reset... session') and distinguishes itself from sibling tools like ultrabrain_analyze or ultrabrain_start.

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 provides no guidance on when to use this tool versus alternatives (e.g., when to reset vs. start a new session with ultrabrain_start). It lacks explicit context for use cases or exclusions, leaving the agent to infer from the tool name alone.

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