helpless_roll

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

With no annotations, the description fully discloses the random d6/d4 outcomes, HP restoration, the death result, and the carer's gating test. This gives the agent a clear model of consequences before invoking.

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 three short paragraphs front-load purpose and timing, then mechanics, then optional carer behavior. No sentences are redundant.

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?

Despite no annotations or output schema, the description covers when to call, what happens, and how the optional parameter changes the roll. This is sufficient for a caller to invoke the tool correctly.

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 richly explains character_id (the downed character) and carer_id (treating ally with a tending effect). The optional reason parameter is not explained, but it has a safe default and is not required for correct invocation.

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 names a specific verb and resource: rolling the Helpless table for a player character at 0 hit points. This clearly separates it from generic sibling rolls like usage_roll or doom_roll.

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?

It gives explicit call timing: 'once the fight ends or the character reaches safety.' It also provides the exact condition for passing carer_id, so an agent knows when to include the optional parameter.

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