manage_combat_state

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

With no annotations, the description carries the behavioral disclosure burden. It explains the advance_turn out-of-bounds behavior (round+1 and reset to zero), the set/clear conditions operation, spell slot updates, and the return shape. This is strong transparent context for a state-mutating tool, though it does not discuss side effects or validation.

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 compact and front-loads the main operations, with the return shape appended for completeness. The slash-separated style is efficient, though slightly terse and potentially ambiguous in the middle segment.

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?

For an 8-parameter tool with no annotations and no output schema, the description covers key behaviors and return values but omits contextual details: there are no examples, no guidance on which parameter combinations are valid, and no statement about destructive effects. It is adequate for basic calls but incomplete for confident autonomous invocation.

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 0%, so the description must compensate. It does explain the semantics of advance_turn, set_conditions, clear_conditions, spell_slots, and implies combatant_id. However, it leaves campaign, encounter, and variant unexplained, and does not clarify how set_conditions and clear_conditions interact or whether operations can be combined.

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 names the tool's specific actions: advancing the initiative cursor, managing combatant conditions, and setting spell slots. It is more specific than the broad name 'manage_combat_state' and distinguishable from siblings like start_encounter or update_campaign_state, though it does not explicitly name an alternative.

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 operations imply usage: an agent would use this when advancing initiative, changing conditions, or updating spell slots during combat. However, there is no explicit when-to-use guidance or exclusion, such as 'use update_campaign_state for non-combat state changes', so the agent must infer the boundary between this and sibling tools.

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