Validate and save character card

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

With no annotations, the description carries the full burden. It discloses the write targets (card.json, card.md) and the implicit name-2 creation on collision, plus the overwrite path for updates, but says nothing about what happens on validation failure, whether partial files are written, or whether existing files are clobbered.

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?

Three short sentences, front-loaded with the action and outputs, followed by the two behavioral rules. Nothing is redundant and the parenthetical redirect is efficiently placed.

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?

The description mentions the return values (id and file paths), which is important with no output schema, and it covers the overwrite path. But for a file-writing mutation with a very large nested schema and no annotations, it should at least indicate validation-failure behavior and whether writes are safe to retry.

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%, so the baseline is 3. The description adds procedural meaning by linking overwrite: true to meta.slug = id for updates, which is genuinely beyond the bare schema, but it says nothing about the card object itself, whose structure the schema already documents exhaustively.

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?

States specific verbs and resource — validates a complete character card and saves it as card.json and card.md — and names the concrete artifacts produced. It also explicitly redirects to character_get for display, so an agent can tell this apart from at least one sibling without opening a schema.

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?

Gives two concrete usage rules: use character_get to show the card, and use overwrite: true with meta.slug = id to update an existing saved card. It does not state what to do when validation fails or how this differs from save-oriented siblings like character_prompt_save, leaving a modest gap.

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