set_bro

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses that the change applies only to the next spawn/respawn/level, not immediately, and clarifies it does not modify the current bro. This is meaningful behavioral context beyond the bare operation, though it does not cover potential errors, persistence, or validation behavior.

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 only two sentences long, front-loads the main action and timing, and appends the key limitation without redundancy. Every word contributes meaning.

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, two clearly documented parameters, and no output schema, the description plus input schema fully equips an agent to call it correctly. The key behavioral nuance (deferred application) is explicitly covered.

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%, with clear descriptions for both broName and playerNum, including an example and a pointer to list_bros. The tool description itself adds little parameter-specific meaning beyond the schema, so the baseline of 3 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 states a clear verb and resource: 'Set which bro the player will spawn as next.' It also defines the timing explicitly with 'on death/respawn/next level' and differentiates itself from a mid-level swap by saying 'Does NOT change the current bro mid-level.' This makes the tool's purpose unambiguous and distinguishable from siblings like swap_bro.

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 clearly explains the tool's scope and timing, and it explicitly warns that it does not change the current bro mid-level, which serves as a useful when-not-to-use signal. However, it does not explicitly name an alternative such as swap_bro or provide more detailed decision guidance, so it stops short of a full usage guideline.

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