galbook_new

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

No annotations are provided, so the description carries the full behavioral burden and says nothing. It does not disclose whether an existing playthrough is discarded, whether a save slot is created, whether the server-side default book/name is used, or what ironman mode actually locks out beyond the terse enum hint in the schema.

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?

Two words plus a Chinese gloss, front-loaded with the action; nothing is wasteful. The brevity is efficient, though it borders on under-specification that is penalized in other dimensions rather than here.

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?

This is a state-initializing tool with six parameters, no annotations, and no output schema, so the description must explain consequences and defaults. It instead provides a two-word label, leaving the agent unable to tell what gets reset or how the omitted book/agent defaults resolve.

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% and all six parameters including three enums are documented in the schema itself, so the baseline is 3. The description adds no extra meaning, such as the effect of hints or the fallback behavior when book/agent are omitted.

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?

"Start a new playthrough" gives a specific verb (start) and resource (playthrough), and the word "new" implicitly separates it from galbook_load / galbook_saves, which resume existing progress. It is clear but does not explicitly name or contrast with those siblings.

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?

There is no statement of when to call this versus galbook_load, galbook_next, or galbook_choose, nor any precondition such as needing a book slug or having no active session. The agent must infer usage from the one-line description and sibling names alone.

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