Set current story

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

Annotations cover safety (readOnlyHint=false, idempotentHint=true, destructiveHint=false); description adds state-effect context (current story changes placement of new elements, floor plan view follows) and returns {currentStory, windowChanged}. Goes beyond what annotations provide.

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 sentences plus a return-value clause, front-loaded with the core action. Every element is relevant, though the return-value mention is slightly redundant with context.

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 2-param mutation tool without output schema or annotations bearing behavior, the description covers effect, default behavior, and return shape. Could explicitly point to get_stories for obtaining valid identifiers, but is otherwise complete.

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% and the schema fully documents the anyOf forms for story and openFloorPlan. Description reinforces the default-true behavior of openFloorPlan and the semantic effect of omitting storyIndex, adding modest 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?

States a specific verb+resource ('Makes a story the current one') and distinguishes it from siblings like get_stories/create_stories. The Navigator double-click analogy concretely clarifies the effect.

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?

Explains consequences of use ('New elements are placed on the current story when no storyIndex is given') and honors the openFloorPlan toggle. Doesn't explicitly route among siblings (e.g., get_stories first to obtain floorId/displayNumber).

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