st.worldbook.create_empty

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

With no annotations, the description carries the full burden, but it only states that the tool creates an empty shell and requires a confirm flag. It does not disclose side effects, whether it can overwrite an existing worldbook, what 'shell' means in terms of state, or what happens if confirm is false. These are material gaps for a mutating tool.

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 short sentences with no filler. The purpose is front-loaded and the confirm requirement is stated separately. Every word earns its place.

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 tool has four parameters, no annotations, no output schema, and zero schema property descriptions. The description is too thin to let an agent safely invoke it: it does not explain the overwrite behavior, the meaning of snapshotLabel, the naming requirements for 'name', or what a successful creation returns. An agent would need to guess on at least three parameters.

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 for the 4 parameters. It adds meaning only to 'confirm' by stating it must be true, but leaves 'name', 'overwrite', and 'snapshotLabel' entirely unexplained. This is inadequate given the complete lack of schema descriptions.

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 and resource ('Create an empty worldbook shell') and adds a purpose clause ('for later entry management') that separates it from sibling tools that inspect, delete, or configure entries. The 'empty' qualifier distinguishes it from entry-level management operations.

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 phrase 'for later entry management' gives clear context for when to use the tool, and 'Requires confirm: true' is a direct usage requirement. It does not explicitly name alternative tools or when not to use it, but the intended workflow is clear.

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