respawn

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

No annotations are provided, so the description carries the full burden. It transparently discloses that this creates a new body at the spawn point and applies the scenario's respawn kit, but it does not mention potential side effects such as item loss, kit consumption, or state resets. This is a moderate gap for a state-changing tool.

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, efficient sentence with no filler. It front-loads the core action ('Create a new body'), then adds the location, trigger, and kit information in a compact way.

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?

With zero parameters and an output schema present, the description covers what an agent needs to invoke the tool correctly: the action, the condition for use, and the result location. It does not explain deeper consequences, but for a zero-argument tool that is not a critical omission.

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 tool has zero parameters, so the input schema already covers everything. The description is not required to explain parameter details, and it does not contradict the schema. The baseline of 4 for a no-parameter tool applies.

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 a specific verb ('Create'), names the resource ('a new body for your character'), and specifies the location ('at the spawn point') and trigger ('after death'). This clearly distinguishes respawn from the many sibling tools, none of which perform this action.

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 phrase '(after death)' explicitly indicates when the tool should be used, providing clear contextual guidance. It does not mention when not to use it or compare against alternatives, but with no sibling performing an equivalent respawn action, the situational cue is sufficient.

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