apply-condition

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

With no annotations provided, the description bears full responsibility. It discloses that the tool authors condition state, describes exhaustion leveling, and explicitly states what it does not do. It could mention side effects like overwriting existing conditions or permission requirements, but overall it is transparent enough.

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 three sentences long, front-loads the core purpose and examples, and wastes no words. Every sentence provides essential information, including usage warnings and references to sibling tools.

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 a tool with 4 parameters and no output schema, the description covers operation, constraints (D&D 5e only), and actor discovery. It lacks error handling info, but the schema covers required fields. It is sufficiently complete for an agent to use 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?

Schema coverage is 100% with descriptions for each parameter. The description adds clarity by explaining exhaustionLevel semantics (0 removes) and that active defaults to true. It provides examples of conditions beyond the schema list, adding value.

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 tool applies or removes conditions on an actor, lists specific conditions, and explicitly says it is not a combat-automation loop, distinguishing it from sibling tools like manage-effect or update-actor.

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 explains when to use (apply/remove conditions), how to remove by setting active=false, and gives alternative tools (list-actors, get-actor) for finding actorIdentifier. It also warns that it does not handle duration countdown or save-ends, preventing misuse.

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