Character

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

No annotations exist, so the description carries the full burden. It does disclose the behavioral repertoire, including a nuance like 'create (quick or step-by-step)' and 'send player signals'. However, it does not state consequences or side effects: whether 'remove' is permanent, what 'stage to roster' persists, or whether 'set_active' changes global state. For a tool with several mutating actions and zero annotations, this is a meaningful gap.

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: one dense enumerative sentence listing the operations, followed by two one-line usage rules. Every sentence earns its place and the guidance is front-loaded. The long comma-separated action list is slightly unwieldy but appropriate for an 11-action dispatch tool.

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 high complexity — 25 parameters, 11 actions, nested objects, no annotations, and no output schema — the description covers selection and routing well but omits several things an agent needs: the roster lifecycle (what 'stage to roster' vs 'roster_remove' vs 'remove' mean), the distinction between entity_id and roster_id, and any sense of return values since no output schema exists. The 100% schema coverage mitigates this, but the description alone does not fully equip an agent to invoke 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 description coverage is 100%, so the baseline is 3. Every parameter already carries an action-context hint in the schema (e.g., 'Entity identifier (stage/sheet/set_active/personality/voice/remove)'). The description itself adds no parameter-level detail, but the schema fully compensates, so no penalty is warranted.

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 ('Manage') and resource ('player characters'), then enumerates the full operation surface: create (quick or step-by-step), stage, import, sheet, set_active, personality/voice, signal, remove, and roster listing. It explicitly differentiates from the npc sibling tool, so an agent can tell exactly what this tool is for.

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?

Provides explicit routing guidance: 'Use when: working with player characters. Do NOT use when: managing NPCs — use npc.' This gives both a positive trigger condition and a named alternative with an exclusion, leaving nothing to inference.

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