Ultrabrain Merge

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

Annotations are neutral (readOnlyHint=false, destructiveHint=false), but the description does not disclose any behavioral traits beyond the basic action. No mention of side effects, permissions, or constraints.

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 clear sentence, which is concise. However, it could be slightly more structured with separated elements, but it achieves readability.

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 5 parameters and no output schema, the description is insufficient. It does not explain the return format, how the strategies differ, or any usage context like prerequisites or typical workflows.

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 60%, but the description adds no additional meaning for parameters like 'strategy', 'create_thought', or 'response_format'. The agent must rely solely on the input schema for parameter understanding.

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 action (merge), the resource (branch insights), and the three possible outputs (synthesis, best-evidence path, or decision note). It distinguishes from sibling tools like ultrabrain_branch or ultrabrain_analyze.

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 when to use the tool (to merge branch insights), but provides no explicit guidance on when not to use it or how it compares to alternatives such as ultrabrain_analyze or ultrabrain_synthesize (which is not a sibling but could be inferred).

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